Airport guidance and safety system incorporating lighting control using GNSS compatible methods

ABSTRACT

An Airport Guidance System and Method which provides for GNSS compatible seamless airport guidance capability is disclosed. The computer system provides a automated lighting functions based upon GNSS based position and spatially compatible databases. The system and method utilize precise GNSS compatible zones, the Earth Centered Earth Fixed (ECEF) WGS-84 coordinate reference frame, GNSS compatible local coordinate frames such as local and state plane grids, zone-based automated airport lighting control, travel path information management processes which allow for the intelligent control of airport lighting systems. True airport independent processing is achieved when the ECEF coordinate reference frame is utilized. The lighting methods and processes are applicable to vehicles and aircraft operating in a controlled airport space envelope as well as other remote user sites with or without the assistance of air traffic controller. The system utilizes broadcast Automatic Dependent Surveillance (ADS) information from participating aircraft and vehicles. Although the processing methods may be employed using other surveillance information derived from radar sources with some degradation in performance due to radar inaccuracies and inability to produce accurate 3-dimensional velocity. The methods and processes employed provide a fundamental framework for increased airport safety, operational efficiency, energy savings and improved automation.

BACKGROUND--FIELD OF THE INVENTION

This invention is a Continuation In Part of parent application 08/117,920 filed Sep. 7, 1993 now U.S. Pat. No. 5,548,515 and divisional elements of application Ser. No. 08/524,081 filed Sep. 6, 1995 for an airport guidance and safety system for use by a pilot or vehicle driver supporting navigation and lighting control using GNSS compatible methods and seamless globally applicable computer automation processing methods with compatible spatial and temporal databases.

BACKGROUND--DESCRIPTION OF PRIOR ART

Today's airport terminal operations are complex and varied from airport to airport. Airports today are, in many cases, the limiting factor in aviation system capacity. Each airport has a unique set of capacity limiting factors which may include, limited tarmac, runways, suitable approaches, navigational or/and Air Traffic Control (ATC) facilities.

Furthermore, operational requirements in the terminal area involve all facets of aviation, communication, navigation and surveillance. The satisfaction of these requirements with technological/procedural solutions should be based upon three underlying principles; improved safety, improved capacity and cost effectiveness.

Today airport air traffic control procedures and general airport aviation operations are based on procedures from the 1950's. These air traffic control procedures were initially developed to separate aircraft while in the air. The separation surveillance system initially was a radar system consisting of a rotating radar antenna. The antenna rotated typically about once every 4.8 seconds while transmitting a signal, another receiving antenna picked up a reflected signal from a target. The surveillance system then calculated a range (based on transit time) and an azimuth angle based on the physical orientation of the antenna. The 2-dimensional position was then usually plotted on a display with other detected targets, objects and clutter. Radar today relies on faster rotating antennas or electronically scanned antennas to provide more frequent updates and higher resolution. To further enhance the performance of the target returns, provide altitude information and an identifier, a transponder is used on the aircraft. The transponder is the key element in radar surveillance systems, since without it no identification and no altitude information is provided to the air traffic control system.

Surveillance data from multiple surveillance systems (radars) is then discretely mosaiced or "tiled" into a semi-continuous system. Controllers today separate traffic visually by the rule of "green in between" the target tracks. This is a highly manual method for separation of aircraft, placing stress on the controllers and limits any true automation assistance for the controller.

Airport lighting functions currently are controller primarily on a manual basis from the airport tower. A 1991 effort conducted by MIT Lincoln Laboratory (DOC #8 Lincoln Lab Journal Vol. 4 #2 1991) used airport surface radar surveillance for the control of airport lights. A localized radar compatible processing environment was used with radar based position reports. The processing was not specifically compatible with seamless globally applicable GNSS position and velocity information nor GNSS based navigation. Other less sophisticated systems using buried magnetic sensors, burried weight sensors and even optical detection systems have been utilized in the control of airport lights. These lighting systems all fail to integrate gracefully into the a GNSS compatible overall airport processing environment as presented here.

In the high density and high precision airport environment numerous single function airport systems have been developed over the years to support air traffic control and pilot needs. Precise landing navigation is currently provided by the Instrument Landing System (ILS), while airside navigation is provided by VOR/DMS, LORAN and NDB's. Airport air traffic controller surveillance is provided thorough visual means, airport surface detection radar (ASDE), secondary surveillance radar, parallel runway monitoring radar and in some cases primary radar. Each of these systems is single function, local in nature and operation and provides accuracy which is a function of distance to the object being tacked. Merging these navigation and surveillance systems into a 4-dimensional seamless airport environment is technically difficult and expensive. MIT Lincoln Laboratories is attempting to provide an improved radar based Air Traffic Control environment and has received three U.S. Pat. Nos. 5,374,932, 5,519,618 and 5,570,095 reflecting those efforts. These patents relate to improvements of the current localized surveillance and navigation airport environment without the use of GNSS compatible seamless techniques as described by Pilley.

These localized systems have served the aviation system well for nearly 50 years and numerous mishaps have been prevented over this period through their use. With the advent of new multi-function technologies superior performance is available at a fraction of the cost of today's current single function systems. The technologies of Global Navigation Satellite Systems, digital communication and low cost commercial computers can support seamless 4-dimensional airport operations at smaller airports unable to justify the heavy financial investment in today's single function navigation and surveillance systems.

BACKGROUND OF THE INVENTOR

The inventor having been involved with the FAA's Advanced Automation System became aware that airport program segments were not getting the attention they deserved, nor were advanced technologies being investigated. The inventor set out to demonstrate that new technologies could be used to support airport navigation, surveillance and lighting control. The multi-year efforts of the inventors are summarized in the book titled: GPS BASED AIRPORT OPERATIONS, Requirements, Analysis, Algorithms U.S. copyright #TX 3 926 573, (Library of Congress #94-69078), (ISBN 0-9643568-0-5). This book provides much of the back ground for this patent application. In addition to the book the following publications and professional papers have been published by the inventor in efforts of due diligence to promote this life saving technology.

PUBLICATIONS

Institute of Navigation, ION GPS-91, Sep. 12, 1991, Technical Paper, "Airport Navigation and Surveillance Using GPS and ADS".

GPS WORLD Magazine, October, 1991, Article, "GPS, Aviation and Airports the Integrated Solution".

71st Transportation Research Board, Annual Meeting, Jan. 14, 1992, Technical Paper, "Applications of Satellite CNS in the Terminal Area".

Institute of Navigation National Technical Meeting, Jan. 28, 1992, Technical Paper, "Terminal Area Surveillance Using GPS".

Institute of Navigation, ION GPS-92, Technical Paper, "Collision Prediction and Avoidance Using Enhanced GPS".

Institute of Navigation, 49th Annual Meeting, June 1993, Technical Paper, "Runway Incursion Avoidance Using GPS".

Airport Surface Traffic Automation Technical Information Group FAA & Industry Forum, Jul. 15, 1993, Presentation.

Commercial Aviation News, Jul. 19, 1993, "Airport Test to Look at Collision Avoidance".

IEEE Vehicle Navigation and Intelligent Vehicle (VNIS), Conference, Oct. 14, 1993, Technical Paper, "Demonstration Results of GPS for Airport Surface Control and Management". Institute of Navigation, ION GPS-93, Sep. 23, 1993, Technical Paper, "GPS for Airport Surface Guidance and Traffic Management". Avionics Magazine, October, 1993, "Differential GPS Runway Navigation System Demonstrated".

IEEE PLANS '94, Apr 1994, Technical Paper, "GPS, 3-D Maps and ADS Provide A Seamless Airport Control and Management Environment".

Institute of Navigation, ION GPS-94, Sep. 22, 1994, Technical Paper, "DGPS for Seamless Airport Operations".

Presentation Seattle, Washington, May 9, 1995. International Civil Aviation Organization of the United Nations, Advanced Surface Movement Guidance and Control (SMGCS) meeting. Presentation and demonstration "GPS based SMGCS".

As the list of presentations and publications shows the inventors have been active in getting the government and the aviation community to accept this life saving cost effective airport technology.

The United States alone currently contains some 17,000 airports, heliiports and seabases. Presently only the largest of these can justify the investment in dedicated navigation and surveillance systems while the vast majority of smaller airports have neither. Clearly, a new approach is required to satisfy aviation user, airport operator, airline and ATC needs.

It would therefore be an advance in the art to provide a cost effective Airport Control and Management System which would provide navigation, surveillance, collision prediction, zone/runway incursion and automated airport lighting control based on the Global Navigation Satellite System (GNSS) as the primary position and velocity sensor on board participating vehicles. It would be still a further advance of the art if this system were capable of performing the navigation, surveillance, collision prediction, lighting control and zone/runway incursion both on board the aircraft/vehicles and at a remote ATC, or other monitoring site.

With the advent of new technologies such as the Global Positioning System, communication and computer technology, the application of new technologies to the management of our airports can provide improved efficiency, enhanced safety and lead to greater profitability for our aviation industry and airport operators.

On Aug. 12, 1993, Deering System Design Consultants, Inc. (DSDC) of Deering, N.H., successfully demonstrated their Airport Control & Management System (AC&M) to the Federal Aviation Administration (FAA). After many years of development efforts, the methods and processes described herein were demonstrated to Mike Harrison of the FAA's Runway Incursion Office, officials from the FAA's Satellite Program Office, the FAA New England Regional Office, the Volpe National Transportation System Center, the New Hampshire Department of Transportation, the Office of U.S. Senator Judd Gregg and the Office of U.S. Representative Dick Swett. This was the first time such concepts were reduced to a working demonstrable system. The inventor has taken an active stand to promote the technology in a public manner and, as such, may have informed others to key elements of this application. The inventor has promoted this technology. The inventor's airports philosophy has been described in general terms to the aviation industry since it was felt industry and government awareness was necessary. The intent of this application to identify and protect through letters of Patent techniques, methods and improvements to the demonstrated system.

With these and other objects in view, as will be apparent to those skilled in the art, the improved airport control and management invention stated herein is unique, novel and promotes the public well being.

SUMMARY OF THE INVENTION

This invention most generally is a system and a method for the control of surface and airborne traffic within a defined space envelope. GNSS-based, or GPS based data is used to define and create a 3-dimensional map, define locations, to compute trajectories, speeds, velocities, static and dynamic regions and spaces or volumes (zones) including zones identified as forbidden zones. Databases are also created, which are compatible with the GNSS data. Some of these databases may contain, vehicle information such as type and shape, static zones including zones specific to vehicle type which are forbidden to the type of vehicle, notice to airmen (notams) characterized by the information or GNSS data. The GNSS data in combination with the databases is used, for example, by air traffic control, to control and manage the flow of traffic approaching and departing the airport and the control of the flow of surface vehicles and taxiing aircraft. All or a selected group of vehicles may have GNSS receivers. Additionally, all or a selected group may have bi-directional digital data and voice communications between vehicles and also with air traffic control. All of the data is made compatible for display on a screen or selected screens for use and observation including screens located on selected vehicles and aircraft. Vehicle/aircraft data may be compatibly superimposed with the 3-dimensional map data and the combination of data displayed or displayable may be manipulated to provide selecting viewing. The selected viewing may be in the form of choice of the line of observation, the viewing may be by layers based upon the data and the objective for the use of the data.

It is, therefore, an object of this invention to provide the following:

1.) A 4-D process logic flow which provides a "seamless" airport environment on the ground and in the air anywhere in the world with a common 3-D coordinate reference and time.

2.) An Airport Control and Management Method and System which utilizes GNSS, 3-D maps, precise waypoint navigation based on the ECEF reference frame, a digital full duplex communication link and a comprehensive array of processing logic methods implemented in developed operational software.

3.) An Airport Control and Management Method and System where a vehicle based 4-D navigational computer and ATC computer utilize the same coordinate reference and precise time standard.

4.) A database management method compatible with 3-D waypoint storage and presentation in 3-D digital maps.

5.) A automated method utilizing the precise 3-D airport map for the definition and creation of airport routes and travel ways.

6.) A 4-D process logic flow which provides precise vehicle waypoint navigation in the air and on the ground. This process allows for monitoring of on or off course conditions for vehicles and aircraft operating within the airport space envelope on board the vehicle.

7.) A 4-D process logic flow which provides precise ATC waypoint navigation mirroring of actual vehicles in the air and on the ground at ATC. This process allows for monitoring of on or off course conditions for vehicles and aircraft operating within the airport space envelope at the ATC computer.

8.) A 4-D process logic flow performed on board the vehicle which provides for precise collision prediction based on 3-dimensional zones.

9.) A 4-D process logic flow performed at the ATC computer which provides for precise collision prediction based on 3-dimensional zones.

10.) A collision detection management method which utilizes the application of false alarm reducing methods.

11.) An ATC process logic flow which detects 3-D runway incursions. The process logic then generates message alerts and controls airport lights.

12.) An ATC zone management method which utilizes the application of false alarm reducing methods.

13.) A vehicle process logic flow which detects 3-D runway incursions. The process logic then generates message alerts and sounds tones within the vehicle or aircraft.

14.) A vehicle zone management method which utilizes the application of false alarm reducing methods.

15.) A 4-D ATC process logic flow which manages ground and air "Clearances" with precise waypoint navigation aboard the vehicle and at the ATC computer.

16.) A 4-D ATC process logic flow which manages ground aid air "Clearances" incorporating an integrated system of controlling airport lights.

17.) A 4-D vehicle process logic flow which manages ground and air "Clearances" with an integrated system of waypoint navigation.

18.) A method of management for 3-D spatial constructs called zones.

19.) A method of management for 3-D graphical constructs called zones.

20.) A method of management for the automated generation of a zones database at any airport.

21.) A database management method for the storage of zones data. Zones database management methods are used aboard the vehicle and at ATC.

22.) A operational management method where the ATC computer provides navigational instructions to vehicles and aircraft. The instructions result in a travel path with clear paths defined being displayed in an airport map.

23.) A operational management method where the ATC computer provides navigational instructions to vehicles and aircraft. The instructions result in waypoints being entered into a 4-D navigation computer.

24.) A datalink message content which supports the above management methods and processes.

25.) A redundant system architecture which satisfies life critical airport operations.

26.) Methods for navigation within the airport environment using map displays, controller clearances and automation techniques in the cockpit and at ATC.

27.) An integrated airport controller automation interface which supports GNSS compatible processing for automated lighting control.

28.) A method for managing GNSS travel path information, clearances and conformance monitoring using broadcast GNSS trajectory information and GNSS compatible PVT.

More specifically, the elements mentioned above form the process framework of the invention stated herein.

BRIEF DESCRIPTION OF DRAWINGS

The invention, may be best understood by reference to one of its structural forms, as illustrated by the accompanying drawings, in which:

FIG. 1 depicts the high-level Airport Control and Management Processing elements and flow.

FIG. 2 represents an example of a cylindrical static zone in a 3-D ALP. This zone could be graphically displayed in a layer of the ALP.

FIG. 3 represents an example of a static zone around a construction area of the airport and is used in zone incursion processing in the vehicles and at the ATC Processor.

FIG. 4 represents an example of a dynamic zone which travels with a moving vehicle, in this case the zone represents the minimum safe clearance spacing which would be used in zone based collision detection processing in the vehicles and at the ATC processor.

FIG. 5 represents an example of a route zone which is defined by navigational waypoints and is used for on/off course processing and is used in the vehicles and at the ATC Processor.

FIG. 6 represents an example of a 3-D ATC zone, used to segregate tracked vehicles to particular ATC stations.

FIG. 7 illustrates the construction of a 3-D runway zone.

FIG. 8 shows a map display with surface waypoints and travel path.

FIG. 9 shows a map display with departure waypoints and travel path.

FIG. 10 illustrates the 4-D collision detection mechanism employed in the Airport Control and Management System.

FIG. 11 depicts a waypoint processing diagram showing the earth and ECEF coordinate system, expanded view of airport waypoints, further expanded view of previous and next waypoint geometry with present position, the cross hair display presentation used in the developed GPS navigator.

FIG. 12 graphs latitude, Longitude plot of a missed approach followed by a touch and go with waypoints indicated about every 20 seconds.

FIG. 13 graphs altitude vs. time for missed approach followed by touch and go, waypoints are indicated about every 20 seconds.

FIG. 14 graphs ECEF X and Y presentation of missed approach followed by a touch and go with waypoints indicated about every 20 seconds.

FIG. 15 graphs ECEF Z versus time of missed approach followed by touch and go, with waypoints about every 20 seconds.

FIG. 16 shows a block diagram of on/off course processing.

FIG. 17 shows a missed approach followed by a touch and go GPS trajectory displayed in a 3-D airport map.

FIG. 18 shows an ECEF navigation screen with navigational window insert and 3-D digital map elements.

FIG. 19 shows the area navigation display with range rings, course and being radial lines, and altitude to true course indicators.

FIG. 20 depicts the GPS sliding cross hair landing display indicating too low (go up) and too far right (turn left).

FIG. 21 illustrates the GPS approach cone with digital map elements showing current position with respect to true course line.

FIG. 22 depicts the demonstration system airport communications diagram showing processor, DGPS base station, radio elements and message flows.

FIG. 23 depicts the demonstration system AC&M hardware block diagram showing various elements of the system.

FIG. 24 depicts the demonstration system aircraft hardware block diagram.

FIG. 25 depicts the demonstration system vehicle #1 hardware block diagram.

FIG. 26 depicts the demonstration system vehicle #2 hardware block diagram.

FIG. 27 shows the navigator display compass rose area navigator and cross hair sliding precision approach display in combination with waypoint information, position, velocity, range to the waypoint, cross track error, speed, heading and distance to true course.

FIG. 28 depicts the airport system single controller station, non redundant design.

FIG. 29 depicts the airport system redundant single controller station.

FIG. 30 depicts the airport system redundant dual controller station.

FIG. 31 depicts the map temporal differential correction system diagram.

FIG. 32 depicts the differential GPS system diagram.

FIG. 33 depicts the closed loop differential DPS system diagram

DESCRIPTION OF PREFERRED EMBODIMENT

AC&M PROCESSING OVERVIEW

The primary Airport Control and Management (AC&M) functions of the invention utilize a Cartesian ECEF X,Y,Z coordinate frame compatible with GNSS. FIG. 1 provides additional detail for the operational elements of the AC&M processing. The GNSS signals broadcast by the vehicles 8 are processed by the Real Time Communication Handler 3 and sent to AC&M Operational Control 1. The Operational Control 1 uses the GNSS data to perform the following processing functions 5 position projections, coordinate conversions, zone detection, collision prediction, runway incursion detection, layer filter, alarm control, and lighting control. If waypoints have been issued to the vehicle 8, mirrored waypoint navigation is also performed by the AC&M processing. The Operational Control 1 interfaces directly to the Graphical Control 2. Graphics messages, including GNSS data and coded information pertaining to zone incursions, possible collision conditions, or off course conditions detected by the AC&M Processing, are passed to the Graphical Control 2. The Graphical Control 2 interprets this data and updates the display presentation accordingly.

The Operational Control 1 function also receives inputs from the Controller/Operator Interface 6. The Controller/Operator Interface uses the data received by Controller/Operator Inputs 7 to compose ATC commands which are sent to the Operational Control 1 function for processing. Commands affecting the presentation on the computer display screen are sent by the Operational Control 1 function to the Graphical Control 2. ATC commands composed by the Controller/Operator Interface 6 processing that do not require further AC&M processing are forwarded directly to the Graphical Control 2 to update the display screen. Both the Operational Control 1 function and Graphical Control 2 processing have access to the Monumentation, Aircraft/Vehicle, Static Zones, Waypoints, Airport Map, ATIS Interface and Airport Status and other low level data bases 9 to process and manipulate the presentation of map and vehicle data on a computer display screen.

More specifically, each vehicle 8 supports the capability to transmit a minimum of an identifier, the GNSS referenced position of one or more antennas, velocity, optional acceleration and time reports. Since this data is broadcast, it is accessible to the airport control tower, other aircraft and vehicles in the local area, and various airline monitoring or emergency command centers which may perform similar processing functions. ATC commands, processed by the Controller/Operator Interface 6 and Operational Control 1 function are passed to the Real Time Communication Handler 3 for transmission to the aircraft/vehicle(s) 8. Upon receipt of ATC messages, the vehicle(s) 8 return an acknowledgment message which is received by the Real Time communication Handler 3 and passed to the Operational Control 1 function. Differential GNSS corrections are generated by the Differential GPS Processor 4 and passed to the Real Time Communication Handler 3 for broadcast to the vehicles. The Real Time Communication Handler 8 performs the following functions at a minimum:

a. Initialize ATC computer communication lines

b. Initialize radio equipment

c. Establish communication links

d. Receive vehicle identifier, positions, velocity, time and other information

e. Receive information from ATC Processor to transmit to vehicle(s)

f. Receive ATC acknowledgment messages from vehicle(s)

g. Transmit information to all vehicles or to selected vehicles by controlling frequency and/or identifier tags

h. Monitor errors or new information being transmitted

i. Receive and broadcast differential correction data

The AC&M techniques and methods described herein provide for GNSS compatible 4-Dimensional Airport Control and Management.

THE 3-D DIGITAL AIRPORT LAYOUT PLAN

The combination of ECEF navigation combined with NAD 83 (Lat, Lon, MSL and State Plane) and WGS 84 (X,Y,Z) based 3-D airport features are necessary in constructing an airport layout plan (ALP). The Airport Control and Management System (AC&M) requires that navigation and Automatic dependent Surveillance (ADS) information used in collision detection processing share the same coordinate frame. The processing methods described herein, require very accurate and properly monumented airport layout plans. Physical features surrounding the airport may be surveyed in a local coordinate frame and, as such, require accurate transformation into the airport map/processing coordinate frame. For these reasons, the use of multi-monumented coordinate references is mandatory for such map construction and survey. Clearly, highly accurate 3-D maps are required when using precise GNSS based navigation, collision avoidance and overall Airport Control and Management for life critical airport applications.

The 3-D ALP database and display presentation support the concept of zones. The display of zone information is managed using the Map Layer Filter. Zones are two and three dimensional shapes which are used to provide spatial cueing for a number of design constructs. Static zones may be defined around obstacles which may pose a hazard to navigation such as transmission towers, tall buildings, and terrain features. Zones may also be keyed to the airport's NOTAMS, identifying areas of the airport which have restricted usage. Dynamic zones are capable of movement. For example, a dynamic zone may be constructed around moving vehicles or hazardous weather areas. A route zone is a 3-D zone formed along a travel path such as a glide slope. Zones processing techniques are also applied to the management of travel clearances and for the detection of runway incursions. Zones may also be associated with each aircraft or surface vehicle to provide collision prediction information.

OPERATIONAL PROJECTIONS

AC&M projection processing utilizes received GNSS ADS messages from a datalink. The complete received message is th en checked for errors using CRC error detection techniques or a error correcting code. The message contains the following information, or a subset thereof, but not limited to:

    ______________________________________                                         PVT ADS DATA                                                                   ______________________________________                                         ID #                   8 Characters                                            VEHICLE TYPE           4 Characters                                            CURRENT POSITION:                                                              X = ECEF X Position (M)                                                                               10 Characters                                           Y = ECEF Y Position (M)                                                                               10 Characters                                           Z = ECEF Z Position (M)                                                                               10 Characters                                           X2 = ECEF X2 Position (M)                                                                             2 Characters *                                          Y2 = ECEF Y2 Position (M)                                                                             2 Characters *                                          Z2 = ECEF Z2 Position (M)                                                                             2 Characters *                                          X3 = ECEF X3 Position (M)                                                                             2 Characters *                                          Y3 = ECEF Y3 Position (M)                                                                             2 Characters *                                          Z3 = ECEF Z3 Position (M)                                                                             2 Characters *                                          VX = ECEF X Velocity (M/S)                                                                            4 Characters                                            VY = ECEF Y Velocity (M/S)                                                                            4 Characters                                            VZ = ECEF Z Velocity (M/S)                                                                            4 Characters                                            AX = ECEF X Acceleration (M/S2)                                                                       2 Characters #                                          AY = ECEF Y Acceleration (M/S2)                                                                       2 Characters #                                          AZ = ECEF Z Acceleration (M/S2)                                                                       2 Characters #                                          TIME                   8 Characters                                            TOTAL CHARACTERS/MESSAGE:                                                                             80 Characters                                           ______________________________________                                          * OPTIONAL FIELD, FOR DETERMINING VEHICLES ATTITUDE IN 3D DIGITAL MAP DAT      BASE                                                                           # OPTIONAL ACCELERATION FIELD                                            

A database is constructed using the ADS message reports. The AC&M processing converts the position and velocity information to the appropriate coordinate frame (if necessary, speed in knots and a true north heading). Simple first and second order time projections based upon position, velocity and acceleration computations are used. The ability to smooth and average the velocity information is also possible using time weighted averages.

ECEF POSITION PROJECTION TECHNIQUE

    PROJECTED X=X+(VX)(t)+(AX)(t.sup.2)/2

    PROJECTED Y=Y+(VY)(t)+(AY)(t.sup.2)/2

    PROJECTED Z=Z+(VZ)(t)+(AZ)(t.sup.2)/2

This set of simple projection relationships is used in the collision prediction and zone incursion processing methods.

ZONE DATABASE

Zone areas may be defined in the initial map data base construction or may be added to the map database using a 2-D or 3-D data entry capability. The data entry device may be used to construct a zone using a digital map in the following manner:

Using the displayed map, the data entry device is used to enter the coordinates of a shape around the area to be designated as a zone. (An example may be a construction area closed to aircraft traffic listed in the current NOTAMS.)

The corners of the polygon are saved along with a zone type code after the last corner is entered. Circles and spheres are noted by the center point and a radius, cylinders are noted as a circle and additional height qualifying information. Other shapes are defined and entered in a similar fashion.

The zone is stored as a list of X, Y, Z coordinates. Lines connecting the points form a geometric shape corresponding to the physical zone in the selected color, line type and style in the proper layer of the base map.

Zone information may then be used by collision detection and boundary detection software contained in the AC&M system. This processing software is explained later in this specification.

FIG. 2 depicts a 3-D cylindrical static zone around a hypothetical utility pole. This zone 10 is added into the airport map 11, while the specific coordinates (center point of base 12, radius of circular base 13, and the height 14) are saved to the zone file list in a convenient coordinate frame.

Below is an example of a zone which is stored in the zone database.

    ______________________________________                                         IDENTIFIER           PARAMETER                                                 ______________________________________                                         Utility pole         Type of Zone                                              Center of base       X, Y, Z                                                   Radius of base       R                                                         Height of the cylinder                                                                              H                                                         ______________________________________                                    

The 3-D digital map 11 is then updated using a series of graphic instructions to draw the zone 10 into the map with specific graphic characteristics such as line type, line color, area fill and other characteristics.

A database of zone information containing zones in surface coordinates such as X & Y state plane coordinates and mean sea level, ECEF reference X, Y, Z and others are accessible to the AC&M Processing. The database may consist of, but is not limited to the following type of zones.

OBJECT OF THE ZONE

TRANSMISSION TOWERS

AIRPORT CONSTRUCTION AREAS

CLOSED AREAS OF AIRPORT

MOUNTAINS

TALL BUILDINGS

AREAS OFF TAXIWAY AND RUNWAY

RESTRICTED AIRSPACE

INVISIBLE BOUNDARIES BETWEEN AIR TRAFFIC CONTROLLER AREAS

APPROACH ENVELOPE

DEPARTURE ENVELOPE

AREAS SURROUNDING THE AIRPORT

MOVING ZONES AROUND AIRCRAFT/VEHICLES

ZONE PROCESSING

The zone information is retrieved from a zone database. As the AC&M Processor receives current ADS reports, information on each position report is checked for zone incursion. Further processing utilizes velocity and acceleration information to determine projected position and potential collision hazards. If a current position or projected position enters a zone area or presents a collision hazard an alert is generated.

A zone is any shape which forms a 2-D or 3-D figure such as but not limited to a convex polygon (2-D or 3-D), or a circular (2-D), spherical (3-D), cylindrical (3-D) or conical shape represented as a mathematical formula or as a series of coordinate points. Zones are stored in numerous ways based upon the type of zone. The coordinate system of the map and the units of measure greatly affect the manner in which zones are constructed, stored and processed.

The invention described herein utilizes four primary types of 2-D and 3-D zones in the Airport Control and Management System.

FOUR PRIMARY ZONE TYPES

The first type zone is a static zone as shown in FIG. 3. Static zones represent static non-moving objects, such as radio towers, construction areas, or forbidden areas off limits to particular vehicles. The zone 15 shown in the FIG. 3 represents a closed area of the airport which is under construction. The zone 15 is a 3-D zone with a height of 100 Meters 16, since it is desired not to have aircraft flying low over the construction site, but high altitude passes over the zone are permitted. An example of a permitted flyover path 17 and a forbidden fly through path 18 are shown in the figure. The fly through will produce a zone incursion, while the flyover will not.

A second zone type is shown in FIG. 4 and represents a dynamic zone 19 which moves with a moving vehicle or aircraft. Dynamic zones may be sized and shaped for rough check purposes or may be used to describe the minimum safe clearance distance. The dynamic zone is capable of changing size and shape as a function of velocity and or phase of flight and characterized by vehicle or aircraft type.

The third type zone is shown in FIG. 5 and is a route zone 20. Route zones are described though the use of travel waypoints 21 and 22. The waypoints 21 and 22 define the center line of a travel path, the zone has a specified allowable travel radius X1, Y1 at Waypoint 1 21 and X2, Y2 at Waypoint 2 22 for the determination of on or off course processing. For simplicity X1 may equal X2 and Y1 may equal Y2. On course 23 operations result in travel which is within the zone, while off course 24 operations result in travel which is outside the zone and result in an off course warning.

The fourth type zone(s) shown in FIG. 6 is a 3-D zone which is dynamic and used to sort ATC traffic by. This type zone is used to segregate information to various types of controller/operator position, i.e. ground control, clearance delivery. Crash Fire and Rescue and others. Travel within a particular zone automatically defines which ATC position or station the traffic is managed by. For example travel within zone 1 25 is directed to ATC ground station, while travel within zone 2 26 is directed to ATC Clearance Delivery position. The ATC zones concept allows for automatic handoff from one controllers position to the other as well as providing overall database the management automation.

The construct of zones is very important to the overall operation of the described invention herein. Further examples of zone processing methods and zone definition is provided below.

EXAMPLE 1

A cylindrical zone on the airport surface constructed using the state plane coordinate system would be represented as the following:

    ______________________________________                                         Center point of circle                                                                         CXsp value, CYsp value                                         Elevation (MSL) Elev = constant, or may be a range                             Circle radius   CR value                                                       ______________________________________                                    

The detection of a zone incursion (meaning that the position is within the 2-D circle) is described below:

    ______________________________________                                         Convert position to State Plane coordinates                                    ______________________________________                                         Current or projected position                                                                    Xsp, Ysp                                                     Subtract circle center                                                                           Xsp - CXsp = DXsp                                            from current position                                                                            Ysp - CYsp = DYsp                                            Determine distance from                                                                          DXsp.sup.2 + Dysp.sup.2 = Rsp.sup.2                          circle center                                                                  Test if position is in                                                                           Rsp < = CR                                                   circle                                                                                           If true continue                                                                 If not true exit not in zone                               Test if position is                                                                              Min Elev < = Elev < = Max Elev                               within altitude range                                                          (a cylindrical zone)                                                           ______________________________________                                    

If the above conditions are met, the position is in the 3-D cylindrical zone. It can be seen that the basic methods used here are applicable to other grid or coordinate systems based on linear distances.

EXAMPLE 2

A cylindrical zone on the airport surface (normal with the airport surface) constructed using the Earth Centered Earth Fixed coordinate system is stored using three axis (X,Y, Z).

    ______________________________________                                         Convert current position to ECEF                                                                 X, Y, Z                                                      Center point of circle                                                                           CX value, CY value, CZ value                                 Circle radius     CR value                                                     Determine distance from                                                                          (X - CX) = DX                                                current or projected position                                                                    (Y - CY) = DY                                                to center of circle                                                                              (Z - CZ) = DZ                                                Determine radial distance                                                                        DX.sup.2 + DY.sup.2 + DZ.sup.2 = R.sup.2                     to circle center point from                                                    current position                                                               Test position to see if it                                                                       R < = CR                                                     is in sphere of radius R                                                                         If true continue                                                                 If not true exit not in zone                               Determine the vector between                                                                     VC = CXE + CYE + CZE                                         the center of the circle                                                       and the center of mass of                                                      the earth                                                                      Calculate its magnitude                                                                          VC.sup.2 = CXE.sup.2 + CYE.sup.2 + CZE.sup.2                 Determine the vector between the                                                                 V = VX + VY + VZ                                             center of mass of the earth and                                                the current or projected position                                              Calculate its magnitude                                                                          V.sup.2 = VX.sup.2 + VY.sup.2 + VZ.sup.2                     Determine the difference between                                                                 V - VC = 0                                                   the two vectors, if result = 0                                                 then in the 2-D zone, if the result                                            is < 0 then position is below, if                                              > 0 then position is above the zone                                            ______________________________________                                    

To check for incursion into an ECEF cylindrical zone, the following is tested for:

    ______________________________________                                         Test if position is                                                                        Min VC < = V < = Max VC                                            within Vector range                                                            (a cylindrical zone)                                                           Where       Min VC represents the bottom of the cylinder                                   Max VC represents the top of the cylinder                          ______________________________________                                    

The final two tests use an approximation which greatly simplifies the processing overhead associated with zone incursion detection. The assumption assumes that over the surface area of an airport, the vector between the center of mass of the earth circular zone center and the vector from the current position to the center of the circle are coincident. That is, the angle between the two vectors is negligible.

The second assumption based on the first approximation is that, rather than perform complex coordinate reference transformations for zone shapes not parallel with the earth's surface, projections normal to the surface of the earth will be used. Zones which are not parallel with the earth's surface are handled in a manner similar to that applied to on or off course waypoint processing using rotation about a point or center line.

EXAMPLE 3

A zone which is shaped like a polygon is initially defined as a series of points. The points may be entered using a data entry device and a software program with respect to the digital map or they may be part of the base digital map. The points are then ordered in a manner which facilitates processing of polygon zone incursion. The following examples indicate how a (4 sided) polygon is stored and how an airport surface zone incursion is performed using both the state plane coordinates and Earth Centered Earth Fixed X, Y, Z coordinates.

    __________________________________________________________________________     Convert Position to SP                                                                          Xsp, Ysp,                                                     State Plane Zone X1sp,Y1sp; X2sp,Y2sp;                                         Vertices         X3sp,Y3sp; X4sp,Y4sp                                          Order in a clockwise                                                           direction                                                                      Height of 3-D zone                                                                              min Elev max Elev                                             Determine min & max                                                                             Xspmax, Xspmin, Yspmax, Yspmin                                values for X & Y                                                               Perform rough check                                                                             Is Xspmin < = Xsp < = Xspmax                                  of current position                                                                             Is Yspmin < = Ysp < = Yspmax                                  or projected position                                                                           If both true then continue with zone checking                                   If not true exit, not in zone                                Calculate the slope                                                                             (Y2sp - Y1sp)/(X2sp - X1sp) = M                               of the line between                                                            points 1 & 2                                                                   Calculate the slope of                                                                          M.sup.-1 = -Mnor                                              the line from the present                                                      position normal to the                                                         line between points 1 & 2                                                      Determine the equation                                                                          Y1sp - M * X1sp = L                                           between points 1 & 2                                                           Determine the equation                                                                          Ysp - Mnor * Xsp = LN                                         for the line normal to the                                                     line between points 1 & 2                                                      and position                                                                   Determine the intersection                                                                      intXsp = (LN - L)/(M - Mnor)                                  of both lines    intYsp = Mnor * intXsp + (Ysp - Mnor * Xsp)                   Determine the offset from                                                                       Xsp - intXsp = DXsp                                           position to intersect                                                                           Ysp - intYsp = DYsp                                           point on the line between                                                      points 1 & 2                                                                   Perform check to see which                                                                      Check the sign of DXsp                                        side of the line the position is on                                                             Check the sign of Dysp                                        (note sign change as function of quadrant & direction in which points are      entered                                                                        in)                                                                            If the point is on the proper                                                                   Meaning the signs are                                         side continue and check                                                                         o.k.                                                          the next line between points                                                   2 & 3 and perform the same                                                     analysis                                                                       If the line is on the wrong                                                    side of the line, then not                                                     in the zone hence exit                                                         If point is on the proper                                                      side of all (4) lines of polygon                                               then in 2-D zone                                                               Note: If the zone vertices are entered in a counter clockwise                  direction the sign of DXsp and DYsp are swapped.                               Test if position is                                                                             Min Elev < = Elev < = Max Elev                                within altitude range                                                          (a 3-D polygon zone)                                                           __________________________________________________________________________

EXAMPLE 4

A further example is provided in the definition of a 3-D runway zone using ECEF X,Y,Z. A list of runway corners is constructed using the 3-D map and a data entry device and an automated software tool. The runway zone is shown in FIG. 7.

The horizontal outline the runway 27 by selecting the four corners C1, C2, C3, C4 in a clockwise direction 28, starting anywhere on the closed convex polygon formed by the runway 27

Define the thickness of the zone (height above the runway)29

The 4 corner 3-D coordinates and min and max altitudes are obtained through the use of a program using the ALP, then conversion are performed if necessary to convert from ALP coordinates to ECEF X, Y, Z values.

    ______________________________________                                         C1 = X1, Y1 ,Z1     C2 = X2, Y2, Z2                                            C3 = X3, Y3, Z3     C4 = X4, Y4, Z4                                            MINALT = SQRT(XMIN.sup.2 + YMIN.sup.2 + ZMIN.sup.2 )                           MAXALT = SQRT(XMAX.sup.2 + YMAX.sup.2 + ZMAX.sup.2)                            HEIGHT = MAXALT - MINALT                                                       ______________________________________                                    

Define the (4) planes formed by the vectors originating at the center of mass of the earth and terminating at the respective four runway corners. Represent the 4 planes by the vector cross product as indicated below:

    ______________________________________                                         XP1 = C1 × C2 XP2 = C2 × C3                                        XP3 = C3 × C4 XP4 = C4 × C1                                        ______________________________________                                    

Store the vector cross products in the polygon zones database, where the number of stored vector cross products equals the number of sides of the convex polygon

Determine if the present position or projected position is within the zone (PP=position to be checked)

    PP=PX1,PY1,PZ1

Determine the scalar Dot product between the current position and the previously calculated Cross Products

    ______________________________________                                         DP1 = PP * XP1      DP2 = PP * XP2                                             DP3 = PP * XP3      DP4 = PP * XP4                                             ______________________________________                                    

If the products are negative then PP is within the volume defined by intersection planes, if it is positive then outside the volume defined by the intersecting planes.

Note: the signs reverse if one proceeds around the zone in a counter clockwise direction during the definition process

Determine if PP is within the height confines of the zone

Determine the magnitude of the PP vector, for an origin at center of mass of the earth.

    PPM=SQRT[(PX1).sup.2 +(PY1).sup.2 +(PZ1).sup.2 ]

Compare PPM=(PP magnitude) to minimum altitude of zone and maximum altitude of zone

    MINALT<=PPM<=MAXALT

If the above relationship is true then in the zone.

If false then outside of the zone

An alternate method of determining if the present position PP is within a zone which is not normal to the earth's surface is determined using a method similar to that above, except that all N sides of the zone are represented as normal cross products, the corresponding Dot products are calculated and their total products inspected for sign. Based upon the sign of the product PP is either cut of or inside of the zone.

An example of actual Zone and Runway Incursion software code is contained shown below. The actual code includes interfaces to light control, clearance status, tones and other ATC functions. ##SPC1##

Since the extension to polygons of N sides based upon the previous concepts are easily understood, the derivation has been omitted for the sake of brevity.

In summary two mathematical methods are identified for detecting zone incursions into convex polygons, one based on the equation and slope of the lines, the other is based on vector cross and dot product operators.

The concept of zones, regardless as to whether they are referenced to surface coordinates, local grid systems or ECEF coordinates, provide a powerful analytical method for use in the Airport Control and Management System.

ZONE BASED CLEARANCES

The airport control and management system manages overall taxi, departure and arrival clearances in a unique and novel manner through the use of zone processing. A departure ground taxi clearance is issued to the selected vehicle. The waypoints and travel path are drawn into the map aboard the selected vehicle. The vehicle(s) then use the presented taxi information to proceed to the final waypoint. AC&M processing uses this clearance information to mask runway zone incursions along the travel path. Since runway incursions are masked for only the selected vehicle and for zones traversed no runway incursion alert actions or warning lights are produced when following the proper course. Should the position represent movement outside of the extablished corridor, an alert is issued signifing an off course condition exist for that vehicle. Upon the vehicle exit from a particular "cleared" zone, the mask is reset for that zone. Once the last waypoint is reached the clearance is removed and the zone mask is reset. The description below details how such clearances are managed.

Surface Departure Clearance Management Method

1. The operator or controller wishes to issue a surface departure clearance to a specific vehicle

2. Through the use of a data entry device such as a touch screen or keyboard or mouse, issue waypoints command is selected for surface departure waypoints

3. The operator is asked to select a specific vehicle from a list of available aircraft and vehicles

4. The vehicle data window then displays a scrollable list of available vehicles contained in a database which are capable of performing operations of departure clearance

5. The operator then selects the specific vehicle using a data entry device such as a touch screen or other data entry device

6. A list is then displayed in a scrollable graphical window of available departure travel paths for the selected vehicle

7. The operator then selects from this list using a data entry device such as a touch screen or other data entry device

8. Upon selection of a particular departure path the waypoints and travel path are drawn into a 3-D ALP. The purpose of presentation is to show the controller or operator the actual path selected

9. The controller or operator is then asked to confirm the selected path. Is the selected path correct? Using a data entry device such as a touch screen or other data entry device a selection is made.

10. If the selected path was not correct, then the command is terminated and no further action is taken

11. If the selection was correct the following steps are taken automatically.

a. AC&M processing sends to the selected vehicle using a radio duplex datalink, the clearance, 4-D waypoint and travel path information

b. The selected vehicle upon receipt of the ATC command replies with an acknowledgment. The acknowledgment is sent over the full duplex radio datalink to the AC&M processing

c. should the AC&M processing not receive the acknowledgment in a specified amount of time from the selected vehicle, a re-transmission occurs up to a maximum of N re-transmissions

d. The vehicle upon receiving the ATC command then "loads" the 4-D navigator with the 4-D waypoint information. A map display contained in the vehicle then draws into the 3-D ALP the departure travel path as shown in FIG. 8. This figure shows travel path as 30 in the digital ALP 31 while actual waypoints are shown as (14) spheres 32.

Departure Clearance Management Method

1. The operator or controller wishes to issue a departure clearance to a specific aircraft

2. Through the use of a data entry device such as a touch screen or keyboard or mouse, issue waypoints command is selected for departure waypoints

3. The operator is asked to select a specific vehicle from a list of available aircraft

4. The vehicle data window then displays a scrollable list of available aircraft contained in a database which are capable of performing operations of departure clearance

5. The operator then selects the specific vehicle using a data entry device such as a touch screen or other data entry device

6. A list is then displayed in a scrollable graphical window of available departure travel paths for the selected vehicle

7. The operator then selects from this list using a data entry device such as a touch screen or other data entry device

8. Upon selection of a particular departure path the waypoints and travel path are drawn into a 3-D ALP. The purpose of presentation is to show the controller or operator the actual path selected

9. The controller or operator is then asked to confirm the selected path. Is the selected path correct? Using a data entry device such as a touch screen or other data entry device a selection is made.

10. If the selected path was not correct, then the command is terminated and no further action is taken

11. If the selection was correct the following steps are taken automatically.

a. AC&M processing sends to the selected vehicle using a radio duplex datalink, the clearance, 4-D waypoint and travel path information

b. The selected vehicle upon receipt of the ATC command replies with an acknowledgment. The acknowledgment is sent over the full duplex radio datalink to the AC&M processing

c. Should the AC&M processing not receive the acknowledgment in a specified amount of time from the selected vehicle, a re-transmission occurs up to a maximum of N re-transmissions

d. The vehicle upon receiving the ATC command then "loads" the 4-D navigator with the 4-D waypoint information. A map display contained in the vehicle then draws into the 3-D ALP the departure travel path as shown in FIG. 9. This figure shows travel path as 34 in the digital ALP 35 while actual waypoints are shown as (5) spheres 36.

12. Upon AC&M receiving the acknowledgment, the following is performed:

a. the zone mask is updated indicating that the selected vehicle has a clearance to occupy runway(s) and taxiway(s) along the travel path. This mask suppresses zone runway incursion logic for this vehicle.

b. the zone based lighting control processing then activates the appropriate set of airport lights for the issued clearance in this case Take Off Lights

13. The vehicle now has active navigation information and may start to move, sending out ADS message broadcasts over the datalink to other vehicles and the AC&M system

14. The selected vehicle ADS messages are received at the AC&M system and at other vehicles.

15. AC&M processing using information contained in the ADS message performs mirrored navigational processing, as outlined in a latter section.

16. Zone incursion checking is performed for every received ADS message using position projection techniques for zones contained in the zones database

17. Should a zone incursion be detected, the zone mask is used to determine if the incurred zone is one which the vehicle is allowed to be in. If the zone is not in the zone mask then a warning is issued. Should the zone be that of a Runway, a Runway Incursion Alert is Issued and the appropriate airport lights are activated.

18. The ADS position is used to determine when the vehicle leaves a zone. When the vehicle leaves the zone, the clearance mask is updated indicated travel though a particular zone is complete. When this occurs the following steps are initiated by the AC&M:

a. the zones mask is updated

b. airport light status is updated

If the exited zone was a Runway, operations may now occur on the exited runway

19. The vehicle continues to travel towards the final waypoint

20. At the final waypoint the navigator and the map display are purged of active waypoint information, meaning the vehicle is where it is expected to be. New waypoints may be issued at any time with a waypoints command function.

AC&M zones based clearance function as presented here provides a unique and automated method for the controlling and managing airport surface and air clearances.

Collision Detection

Collision detection is performed through the zones management process. The basic steps for collision detection and avoidance are shown below in a general form. FIG. 10 shows graphically what the following text describes.

1. Vehicle Position, Velocity and Time (PVT) information are received for all tracked vehicles. The following processing is performed for each and every ADS vehicle report

2. PVT information is converted to the appropriate coordinate system if necessary and stored in the database

3. A rough check zone 38 and 39 is established based on the current velocity for each vehicle in the database

4. Every vehicle's rough check radius is compared with every other vehicle in the database. This is done simply by subtracting the current position of vehicle V from the position of vehicle V+1 in the database to determine the separation distance between each vehicle and every other vehicle in the database. This is performed in the ECEF coordinate frame.

5. For each pair of vehicles in the database that are within the sum of the two respective rough check radii values; continue further checking since a possible collision condition exists, if not within the sum of the rough check radii do no further processing until the next ADS message is received

6. For each set of vehicles which have intersecting rough check radii project the position ahead by an increment of Time (t) using the received vehicle velocity and optionally acceleration information. Projected positions at time=T1 are shown by two circles 40 and 41 the minimum safe clearance separation for the fuel truck R1 and aircraft R2 respectively.

7. Determine the new separation distance between all vehicles which initially required further checking. Compare this distance to the sum of minimum safe clearance distances R1 and R2 for those vehicles at the new incremented time. The minimum safe clearance distances R1 and R2 are contained in a database and is a function of vehicle velocity and type. Should the separation distance 42 between them be less than the sum of the minimal safe clearance distances R1+R2, then generate alert warning condition. Record the collision time values for each set of vehicles checked. If no minimum safe clearance distance is violated then continue checking the next set of vehicles in a similar fashion. When all vehicles pairs are checked then return to the start of the vehicle database.

8. Increment the projection time value (T+t) seconds and repeat step 7 if separation was greater than the sum of the minimal safe separation distance R1+R2. Continue to increment the time value to a maximum preset value, until the maximum projection time is reached, then process next pair of vehicles in a similar fashion, until the last vehicle is reached at that time start the process over. If minimum safe clearance (R1+R2) was violated compare the time of intersection to the previous time of intersection. If the previous intersection time is less than the new intersection time the vehicles are moving apart, no collision warning generated. In the event that the vehicles are moving together, meaning the intersection times are getting smaller, determine if a course change is expected based upon the current waypoints issued, and if the course change will eliminate the collision condition. If a course change is not expected or if the course change will not alleviate the collision situation then generate alert. If the projection time T is less than the maximum projection time for warning alerts, generate a warning. If the projection time T is greater than the maximum projection time for a warning alert and less than the maximum projection time for a watch alert, generate a watch alert. If the projection time T is greater than the maximum projection time for a watch alert generate no watch alert.

9. The warning condition generates a message on the ALERT display identifying which vehicles are in a collision warning state. It also elevates the layer identifier code for those vehicle(s) to an always displayed (non-maskable) warning layer in which all potentially colliding vehicles are displayed in RED.

10. The watch condition generates a message on the ALERT display identifying which vehicles are in a collision watch state. It also elevates the layer identifier code for that vehicle(s) to an always displayed (non-maskable) watch layer in which all potentially colliding vehicles are displayed in YELLOW.

11. The process continually runs with each new ADS message report.

Collision Processing Software Example

The same code below performs the above collision processing, without the routine which checks for course changes, to reduce false alarms.

    __________________________________________________________________________     /**********************************************************************        File Name : collpred.c                                                         Description :                                                                        collpred.c contains the routines which update the vehicle                      database and perform collision prediction algorithms.                    Units                                                                             : get.sub.-- veh.sub.-- index,                                                 store.sub.-- remote.sub.-- msg,                                                chk.sub.-- for.sub.-- collisions                                               convert.sub.-- veh                                                          /*----------------------------------------------------------------------*/     #include <stdio.h>                                                             #include <string.h>                                                            #include <stdlib.h>                                                            #include <graph.h>                                                             #include <math.h>                                                              #include "veh.h"                                                               #include "sio.h"                                                               #include "coord.h"                                                             #include "color.h"                                                             #include "rtzones.h"                                                           #include "lights.h"                                                            /*#include "txlib.h" */ /* tx library functions   */                           #define DEF.sub.-- SEP 100000                                                  /*----------------- external procedures ----------------------------*/         /*---- coordinate convertion routines ----*/                                   /*extern POINT *convert.sub.-- ecef.sub.-- to.sub.-- dd(POINT *pp);*/          /*----------------- external variables -----------------------------*/         extern short num.sub.-- vehs;                                                                  /* number of vehicles in database  */                          extern char veh.sub.-- id[8];                                                                  /* id of current vehicle   */                                  extern short veh.sub.-- type;                                                                  /* type of vehicle   */                                        extern short gpsveh.sub.-- type;                                                               /* type of vehicle   */                                        extern short veh.sub.-- clear.sub.-- status;                                                   /* clearance status for vehicle   */                           extern double cur.sub.-- radius;                                                               /* radius of present position for zones  */                    extern short min.sub.-- .sub.-- warning;                                                       /* min secs prior to collision alert  */                       extern short mid.sub.-- warning;                                                               /* mid range number of secs prior to alert*/                   extern double proj.sub.-- time;                                                                /* time used in projection of position */                      extern short max.sub.-- coll.sub.-- count;                                                     /* num coll detections prior to alert */                       extern short layer;                                                                            /* graphics layer for vehicle  */                              extern int rnwy.sub.-- incursion;                                                              /* indicates previous runway incursion */                      extern int zone.sub.-- incursion;                                                              / * indicates previous zone incursion */                       extern double max.sub.-- proj.sub.-- time;                                                      /* maximum number of seconds in projection*/                  extern short inside.sub.-- zone;                                                               /* flag indicating pp is in static zone */                     extern short veh.sub.-- update;                                                                /* flag indicating new vehicle data  */                        extern short vehnum;                                                                           /* vehicle number (based on id)  */                            extern int total.sub.-- wps[MAX.sub.-- VEHS];                                                   total waypoints in current wp list */                         extern short current.sub.-- clearance;                                                          /* set if any vehicle is cleared */                           extern short end.sub.-- of.sub.-- wps;                                                          /* end of waypoint processing  */                             extern short off.sub.-- course;                                                                /* flag indicating veh is off course */                        extern short wrong.sub.-- way;                                                                  /* flag indicating veh is wrong way */                        extern double xtrack;                                                                          /* cross track error   */                                      extern double range[MAX.sub.-- VEHS];                                                          /* range value stored for each vehicle*/                       extern char veh.sub.-- cleared[8];                                                             /* vehicle cleared for landing/takeoff*/                       extern FILE *colfile;                                                          /*short in.sub.-- coll.sub.-- zone;*/                                                          /* flag indicating pp is outside of zone */                    short curr.sub.-- color;                                                                        /* current color                                              short coll.sub.-- condition;                                                                    /* flag indicating coll watch/warning  */                     int prev.sub.-- rnwyincur;                                                                     /* indicates previous runway incursion */                      short prev.sub.-- layer;                                                                        /* graphics layer for vehicle  */                             /*-------------------- global data -------------------------*/                 short vindex;   /* index into vehicle database */                              VEHICLE.sub.-- DATA veh[MAX.sub.-- VEHS]; /* vehicle database   */             /*----------------------------------------------------------------------       Unit Name:      store.sub.-- remote.sub.-- veh                                 __________________________________________________________________________

Description: parses the veh₋₋ str and stores the data in the vehicle database. The incoming veh₋₋ str has the following format:

    veh.sub.-- id veh.sub.-- type ecefx ecefy ecefx velx vely velz course

This function is called by the vehicle processing whenever a remote message is received. In the ATC processor, collision prediction is performed each time a remote message is received. After the collision prediction processing, store₋₋ remote₋₋ veh is called to update the vehicle database. ##SPC2##

On or Off Course Processing

The AC&M processing performs mirrored navigational processing using the same coordinate references and waypoints as those aboard the vehicles. In this manner the ATC system can quickly detect off course conditions anywhere in the 3-D airport space envelope and effectively perform zone incursion processing aboard the vehicles and at the AC&M.

The AC&M processing software converts the position and velocity information to the appropriate coordinate frame (zone & map compatible) using techniques described previously. Waypoints based upon the precise 3-dimensional map are used for surface and air navigation in the airport space envelope. The capability is provided to store waypoints in a variety of coordinate systems, such as conventional Latitude, Longitude, Mean Sea Level, State Plane Coordinates, ECEF X, Y, Z and others. The navigational waypoint and on course-off course determinations are preferred to be performed in an ECEF X, Y, Z coordinate frame, but this is not mandatory.

The following mathematical example is provided to show how waypoints and trajectories are processed in Latitude, Longitude, Mean Sea Level and in ECEF X, Y, Z. An actual GNSS flight trajectory is used for this mathematical analysis. The flight trajectory has been previously converted to an ECEF X, Y, Z format as have the waypoints using the previously described techniques. FIGS. 11, 12, 13, 14, 15 are used in conjunction with the following description.

FIG. 11 depicts the ECEF waypoint processing used in the AC&M. The ECEF coordinate system 43 is shown as X, Y, Z, the origin of the coordinate system is shown as 0,0,0. The coordinate system rotates 44 with the earth on its polar axis. The airport 45 is shown as a square patch. An enlarged side view of the airport 46 is shown with (4) waypoints 47. A further enlargement shows the Present Position 48 (PP), the Next Waypoint 49 (NWP) the Previous Waypoint (PWP) 50. The true Course Line 58 is between the Next Waypoint 49 and Previous Waypoint 50. The vector from the Present Position 48 to the Next Waypoint 49 is vector TNWP 51. The Velocity Vector 52 and the Time Projected Position is shown as a solid black box 53. The Projected Position 53 is used in zone incursion processing. The 3-D distance to the true coarse is represented by the Cross Track Vector 54 XTRK. The vector normal to the earth surface at the present position and originating at the center of mass of the earth is shown as 55. This vector is assumed to be in the same direction of the vertical axis 56. The lateral axis 57 is perpendicular to the vertical axis and perpendicular to the true course line 58 between the Next Waypoint 49 and the Previous Waypoint 50. The Navigational Display 59 shows the Present Position 48 with respect to the True Course Line 58.

The following equations describe the processing performed in the AC&M while FIGS. 12, 13, 14, and 15 represent plots of the actual trajectory information.

    __________________________________________________________________________     Variable Definition                                                            Ω =                                                                              the number of degrees per radian                                                               57.295779513                                           α =                                                                              semi major axis, equatorial radius                                                             6378137 meters                                         e =     earth's eccentricity                                                                           0.0818182                                              TALT =  ellipsoidal altitude of trajectory position (meters)                   WALT =  ellipsoidal altitude of the waypoint positions (meters)                ρ = earth's radius of curvature at the position or waypoint                r =     2-d equatorial radius (meters)                                         R =     first estimate of the radius of curvature (meters)                     sφ =                                                                               the ratio of ECEF Z value divided by R (meters)                        RC =    radius of curvature at the present position (meters)                   h =     altitude with respect to the reference ellipsoid (meters)               =      longitude of position in radians                                       φ = latitude of position in radiams                                        ENU =   East, North, Up coordinate reference                                   XYZ =   East, North, Up vector distance (meters) to waypoint                   VELENU =                                                                               East, North, Up velocity in (meters/sec)                               DISTENU =                                                                              East, North, Up scalar distance to waypoint                            VELEMUMAG =                                                                            East, North, Up Velocity magnitude (scalar) meters/sec                 NBEAR = True North Bearing                                                     T = Time in seconds                                                            p.sub.wT = Earth's radius of curvature at the waypoint                         Waypoint indexes through a list of waypoints                                   Waypoints are indexed as a function of position                                p.sub.T = Earth's radius of curvature at the GNSS position                     Position                                                                       LA.sub.T = Latitude  LO.sub.T = Longitude  TALT.sub.T = altitude               Waypoint                                                                       WLA.sub.wT = Waypoint Lat.  WLO.sub.wT = Waypoint Lon.  WALT.sub.wT =          altitude                                                                       Position                                                                       X.sub.T = ECEF X  Y.sub.T = ECEF Y  Z.sub.T = ECEF Z                           Waypoint                                                                       A.sub.T = Waypoint ECEF X  B.sub.T = Waypoint ECEF Y  C.sub.T = Waypoint       ECEF Z                                                                         EARTH RADIUS OF CURVATURE DETERMINATION                                         ##STR1##                                                                                          ##STR2##                                                   AT WAYPOINT        AT GNSS POSITION                                            CONVERT TRAJECTORY TO ECEF COORDINATES                                         X.sub.T := (TALT.sub.T + ρ.sub.T) · cos (LA.sub.T)                · cos (LO.sub.T)                                                      Y.sub.T := (TALT.sub.T + ρ.sub.T) · cos (LA.sub.T)                · sin (LO.sub.T)                                                      Z.sub.T := [TALT.sub.T - ρ.sub.T · (1 - e.sup.2)] ·      sin (LA.sub.T)                                                                 CONVERT WAYPOINTS TO ECEF COORDINATES                                          A.sub.wT := (WALT.sub.wT + ρ.sub.wT) · cos (WLA.sub.wT)           · cos (WLO.sub.wT)                                                    B.sub.wT := (WALT.sub.wT + ρ.sub.wT) · cos (WLA.sub.wT)           · sin (WLO.sub.wT)                                                    C.sub.wT := [WALT.sub.wT + ρ.sub.wT · (1 - e.sup.2)               · sin (WLA.sub.wT)                                                    FIND VECTOR FROM PRESENT POSITION TO NEXT WAYPOINT                             T = TIME OF TRAJECTORY DATA MATRIX INDEX                                       TIME INTO TRAJECTORY = 61 SECONDS                                              CONSTRUCT ECEF WAYPOINT MATRIX Q                                                ##STR3##                                                                      WAYPOINT SELECTION CRITERIA #1 TIME BASED                                      TIME BASED WAYPOINT SELECTION TECHNIQUE                                        DETERMINE NEXT WAYPOINT FROM PRESENT POSITION                                   ##STR4##                                                                      WAYPOINT SELECTION CRITERIA #2 POSITION BASED                                  UTILIZES THE CONCEPT OF ZONES, SEE ZONES                                        ##STR5##                                                                      DETERMINE VECTOR BETWEEN PREVIOUS AND THE NEXT WAYPOINT                        Qa := (Q.sub.a+1,0 - Q.sub.a,0 Q.sub.a+1,1 - Q.sub.a,1 Q.sub.a+1,2 -           Q.sub.a,2)                                                                     PP := (X.sub.T Y.sub.T Z.sub.T)   PRESENT POSITION                             NWP := [A.sub.N·(1+a) B.sub.N·(1+a) C.sub.N·(1+     a) ]   NEXT WAYPOINT                                                           TNWP := NWP - PP   VECTOR DISTANCE TO THE NEXT WAYPOINT                        AT FLIGHT TIME T = 61 SECONDS, THE NEXT WAYPOINT IS THE                        FOLLOWING X, Y, Z DISTANCE FROM THE CURRENT POSITION                           TNWP = (-394.0104406164  424.5394341322  588.6638708804)                       DETERMINE THE MAGNITUDE OF THE DISTANCE TO THE WAYPOINT                         ##STR6##                                                                      DIST = 825.8347966318 METERS                                                   NEXT DETERMINE IF THE SPEED SHOULD REMAIN THE SAME, OR                         CHANGE                                                                         TIME EXPECTED AT NEXT WAYPOINT IS 80 SECONDS INTO TRAJECTORY                   CURRENT VELOCITY IS BASED UPON GNSS RECEIVER DETERMINATION                      ##STR7##                                                                      VX = -20.7373916114 M/S X ECEF VELOCITY TO REACH WAYPOINT ON TIME              COMPARE CURRENT X VELOCITY TO REQUIRED X VELOCITY, IF LESS                     INCREASE IN VELOCITY, IF GREATER THAN REQUIRED VELOCITY                        DECREASE VELOCITY                                                               ##STR8##                                                                      VY = 22.3441807438 M/S Y ECEF VELOCITY TO REACH WAYPOINT ON TIME               COMPARE CURRENT Y VELOCITY TO REQUIRED Y VELOCITY, IF LESS                     INCREASE IN VELOCITY, IF GREATER THAN REQUIRED VELOCITY                        DECREASE VELOCITY                                                               ##STR9##                                                                      VZ = 30.9823089937 M/S Z ECEF VELOCITY TO REACH WAYPOINT ON TIME               COMPARE CURRENT Z VELOCITY TO REQUIRED Z VELOCITY, IF LESS                     INCREASE IN VELOCITY, IF GREATER THAN REQUIRED VELOCITY                        DECREASE VELOCITY                                                               ##STR10##           VELOCITY MAGNITUDE                                        VELECEF = 43.4649892964 M/S                                                    VELECEF := (-20.737 22.344 30.982)                                             DETERMINE THE ON COURSE OFF COURSE NAVIGATIONAL DATA                           UNIT VECTOR PERPENDICULAR TO PLANE OF QA AND TNWP                               ##STR11##                                                                                     ##STR12##                                                      UNIT VECTOR PERPENDICULAR TO PLANE OF QA AND NP                                 ##STR13##                                                                                     ##STR14##                                                      CROSS TRACK ERROR                                                              XTRK := UN · TNWP.sup.T                                               XTRK = 28.5392020973                                                           CALCULATE CROSS TRACK VECTOR                                                         VXTRK := XTRK · UN                                                              ##STR15##                                                      UNIT VECTOR FROM PRESENT POSITION TO NEXT WAYPOINT                              ##STR16##                                                                                     ##STR17##                                                      UNIT VECTOR OF PRESENT POSITION                                                 ##STR18##                                                                                     ##STR19##                                                      UNIT VECTOR OF NEXT WAYPOINT                                                    ##STR20##                                                                                     ##STR21##                                                      CHECK AGAINST GREAT CIRCLE TECHNIQUE                                           GREAT CIRCLE ANGLE β := acos (UNWP · UPP)                        β · Ω = 0.0074290102 DEGREES                               DETERMINE RANGE TO NEXT WAYPOINT FROM PRESENT POSITION                         h = 0 SHOULD BE THE SAME AS DIST WHEN ALT IS NEARLY AT ELLIPSOID                ##STR22##      R3 = 825.7511698494 R3 - DIST = -0.0836267824                  METERS       METERS                                                            `THe ECEF ANALYSIS COMPARES TO GREAT CIRCLE ANALYSIS VERY                      CLOSELY`                                                                       CONVERTING BACK TO LAT. LON AND MSL                                            DETERMINE GEODETIC PARAMETERS (LAT, LON & EL)                                   ##STR23##                                                                                     ##STR24##                                                       ##STR25##                                                                      ##STR26##                                                                                ##STR27##    h = 287.6967718417                                      ##STR28##                                                                                ##STR29##     · Ω = -71.40645  φ ·                           Ω = 42.930575339                                    CONVERT TO ENU COORDINATES                                                      ##STR30##                                                                     FIND ENU VECTOR FROM PRESENT POSITION TO NEXT WAYPOINT                         EAST DISTANCE                                                                  NORTH DISTANCE                                                                 UP DISTANCE                                                                          XYZ := ENU · (TNWP.sup.T)                                                       ##STR31##                                                      EAST VEL.                                                                      NORTH VEL.                                                                     UP VEL                                                                               VELENU := ENU · (VELECEF.sup.T) M/S                                               ##STR32##                                                     ##STR33##                                                                     DIST = 825.8347966318 METERS                                                    ##STR34##                                                                     VELENUMAG = 43.4644892872 M/S                                                  THE ECEF APPROACH AND THE ENU APPROACH PRODUCE THE SAME                        RESULTS SO IT IS POSSIBLE TO USE EITHER COORDINATE REFERENCE                   TO CONTROL THE NECESSARY SPEED TO THE WAYPOINT                                 FIND TRUE NORTH BEARING ANGLE TO NEXT WAYPOINT USING TANGENT                    ##STR35##        NBEAR = -16.7581666051 DEGREES                               ADJUST FOR TRIGONOMETRIC QUADRANTS AND YOU HAVE THE TRUE                       BEARING                                                                        __________________________________________________________________________

Should the Range to the Waypoint become larger than the previous range of the waypoint a waypoint may not have automatically indexed. This situation could occur if the vehicle did not get close enough to the waypoint to index automatically or an ADS message may have been garbled and the waypoint did not index, due to a lost ADS message. In this case the following analysis is performed:

a) temporarily increment the waypoint index

b) find the vector between the vehicles present position (PP) and the next waypoint (NWP)

    Vector to the next waypoint, TNWP=NWP(X, Y, Z)-PP(X, Y, Z)

c) Determine the current vehicle velocity vector

    VEL=(VX, VY, VZ)

d) Determine the Dot Product between the Velocity Vector and Vector TNWP

    COS θ=TNWP dot VEL

e) If A<COS θ<B then keep current waypoint index

Where A and B are between 0 and 1 and represent an adjustable value based on the allowable vehicle velocity angular deviation from the true course.

If -1<COS θ≦0 then return to previous waypoint index and generate wrong way alert

The above technique can be expanded to include curved approach, using cubic splines to smooth the transitions between waypoints. A curved trajectory requires changes to the above set of equations. Using the technique of cubic splines, one can calculate three cubic equations which describe smooth (continuous first and second derivatives) curves through the three dimensional ECEF waypoints. The four dimensional capability is possible when the set of cubic equations is converted into a set of parametric equations in time. The table below depicts an ECEF waypoint matrix which is used in cubic spline determinations.

Typical Waypoint ECEF Matrix

The AC&M processing utilizes the combination of precise ECEF X, Y, Z navigation and waypoints. Waypoints may be stored in a data file for a particular runway approach, taxi path or departure path. Waypoints may be entered manually, through the use of a data entry device. A list of waypoints describing a light and or taxi trajectory is then assigned to a particular vehicle. To further supplement waypoint processing expected arrival time may be added to each waypoint as well as velocity ranges for each phase of flight. In this manner, 4 dimensional airport control and management is provided utilizing a GNSS based system. Mathematical processing is used in conjunction with precise waypoints to define flight trajectories. The mathematics typically uses cylindrical shapes but is not limited to cylinders, cones may also be used, and are defined between adjacent waypoints. Typical on or off course processing is outlined below and is shown in FIG. 16.

EXAMPLE 1 Missed Waypoint, With Off Course Condition

a. Construct the True Course line between the previous waypoint 61 and the next waypoint 62

b. Determine the shortest distance (cross track error 64) from the current position 63 to the line 60 between the previous waypoint 61 and the next waypoint 62

c. Determine the magnitude of cross track error

d. Compare the magnitude of the cross track error to a predefined limit for total off course error shown as 65 in the figure.

e. Construct an mathematical cylindrical zone centered on the line between the previous 61 and next waypoint 62 with radius equal to the off course threshold 65.

f. If the magnitude of the cross track error 64 is greater than the off course threshold 65 then raise flag and generate alert (off course).

g. Determine the necessary velocity to reach next waypoint on schedule, as shown previously

h. Is necessary velocity within present limits or guidelines?

i. Check actual current velocity against preset limits and necessary velocity, If above present limits, raise flag and issue alert to slow down. If below preset limits, raise flag and issue alert to speed up

j. Automatically index to the following waypoint 66 when the position is within the index waypoint circle 67

k. Should wrong way be detected (positions 68 and 69), index ahead to the next to waypoint pair 66 and 62 and check direction of travel 71 (Velocity) against the line 72 between the waypoints 66 and 62, if the direction of travel is within a preset angular range 70 (A to B degrees) and not off course. If the check is true meaning not off course and headed towards next waypoint then index permanently to waypoint set 66 and 62, no alert generated.

l. In the event that an off course condition and wrong way occur (position 69) a message is formatted which updates the layer filter for the target which is off course, an alert is generated, the waypoints are returned to the initial settings and action is taken to bring vehicle back on course possibly using a set of new waypoints

m. In the event of a velocity check which indicates that the speed up or slow down velocity is outside of an approved range, generate a warning the speed for vehicle is out of established limits, Preset speed over ground limits are adjusted for current air wind speed.

n. The controller reviews the situation displayed and if necessary invokes a navigational correction message to be sent to the Real Time Communication Handler, and then broadcast by radio the aircraft off course or flying at the wrong speed. The controller at this time may change the expected arrival time at the next waypoint if so necessary

EXAMPLE 2 Missed Waypoint, With On Course Processing

a. Construct the True Course line between the previous waypoint 66 and the next waypoint 72

b. Determine the shortest distance (cross track error 73) from the current position 74 to the line between the previous waypoint 66 and next waypoint 72

c. Determine the magnitude of cross track error

d. Compare the magnitude of the cross track error to a predefined limit for total off course error shown as 75 in the figure.

e. Construct an mathematical cylindrical zone centered on the line between the previous waypoint 66 and next waypoint 72 with radius equal to the off course threshold 75

f. If the magnitude of the cross track error 73 is greater than the off course threshold 75 then raise flag and generate alert (off course).

g. Determine the necessary velocity to reach next waypoint on schedule, as shown previously

h. Is necessary velocity within preset limits or guidelines?

i. Check actual current velocity against preset limits and necessary velocity, If above preset limits, raise flag and issue alert to slow down. If below preset limits, raise flag and issue alert to speed up

j. Automatically index to the following waypoint 76 when the position is within the index waypoint circle 77

k. Should wrong way be detected (position 74), index ahead to the next to waypoint pair 76 and 72 and check direction of travel 78 (Velocity) against the the line 80 between the waypoints 76 and 72, if the direction of travel is within a preset angular range 79 (A to B degrees) and not off course. If the check is true meaning not off course and headed towards next waypoint then index permanently to waypoint set 76 and 72, no alert generated

l. In the event of a velocity check which indicates that the speed up or slow down velocity is outside of an approved range, generate a warning the speed for vehicle is out of established limits, Preset speed over ground limits are adjusted for current air wind speed.

m. The controller reviews the situation displayed and if necessary invokes a navigational correction message to be sent to the Real Time Communication Handler, and then broadcast by radio to the aircraft off course or flying at the wrong speed. The controller at this time may change the expected arrival time at the next waypoint if so necessary

The AC&M processing performs all on or off course processing determinations and the displays information related to on or off course or late or early arrival conditions.

Alert Display Function

Within the AC&M system collision alerts, zone, off course and improper speed warnings are handled somewhat differently than normal position updates. When the AC&M processing recognizes a warning condition, the aircraft(s)/vehicle(s) involved are moved to a special ALP layer. The layer filter controls what graphic parameters a particular vehicle or aircraft is displayed with. The change in the layer from the default vehicle layer signifies that the target has been classified as a potential collision, zone intrusion risk, off course condition or improper speed.

AC&M Control Zones

ATC Control Zones are used to sort and manage air and surface traffic within the airport space envelope. The AC&M Control Area is divided into AC&M Control Zones. Typically the outer most airport control zone interfaces with an en route zone. Aircraft within the 3-D AC&M zone transmit their GNSS derived positions via an on board datalink. The GNSS data is received by the airport AC&M equipment. The AC&M Processing determines the ECEF AC&M Control Zone assignment based on the aircraft's current position and assigns the aircraft to the map layer associated with that Control Zone. Mathematical computations as defined previously, are used to determine when a vehicle is in a particular control zone.

As an aircraft enters the AC&M or transitions to another ATC Control Zone, a handoff is performed between the controllers passing and receiving control of that aircraft. Surface traffic is handled in the same manner. With this AC&M scenario, each controller receives all target information but suppresses those layers that are not under his control. In this manner the controller or operator views on those vehicles or aircraft in his respective control zone. Should there be a collision condition across an ATC zone boundary the conflicting vehicles will be displayed in a non-supressable layer.

All targets within an AC&M Control Zone would be placed in the appropriate map layer for tracking and display purposes. Layer coding for each tracked target can be used to control graphic display parameters such as line type, color, line width as well as be used as a key into the underlying database for that object.

Additional AC&M Control Zones may be defined for other surface areas of the airport, such as construction areas, areas limited to specific type of traffic, weight limited areas and others. These areas may be handled through ATC but will most or be controlled by airline or airport maintenance departments. The concept of a zone based AC&M system integrated with 3-D map information provides a valuable management and navigational capability to all vehicles and aircraft within the airport space envelope.

Entering Waypoints

The AC&M processing defined herein allows the user to enter waypoints using the digital map as a guide. To enter a series of waypoints the controller simply uses the map which may provide plan and side views of the airport space envelope. The cursor is moved to the appropriate point and a selection is made by pressing a key. The position is then stored in a list with other waypoints entered at the same time. The user is then prompted to enter a name for the waypoint list and an optional destination. Lastly, the waypoints converted the appropriate coordinate frame and are then saved to a file or transmitted to a particular vehicle. In this manner the user may add and define waypoints.

DEFINING ZONES

The user may define zones using the digital map as a guide. To enter a series of zones the controller simply uses the map which may provide plan and side views of the airport space envelope. The cursor is moved to the appropriate point and a selection is made by pressing a key. The position is then stored in a list with other zone definition points. The controller is then prompted to enter a name for the zone (pole, tower, construction area, etc.) and type of zone (circle, sphere, box, cylinder, etc.). Lastly, the zones are converted to the appropriate coordinate frame and saved to a file or transmitted to a particular vehicle. In this manner the user may define additional zones.

The ability to quickly and accurately define zones is key to the implementation of a zones based AC&M capability.

ADS MESSAGE FORMAT CONSIDERATIONS

The definition and standardization of a `seamless` aviation system datalink format(s) is critical to the implementation of a GNSS-based aviation system.

SAMPLE ADS MESSAGE FORMAT

Perhaps the most basic issue which must be resolved in the determination of the datalink format, is the selection of the coordinate system and units for the GNSS-derived position and velocity data. Compatibility with digital and paper maps, navigation system and overall mathematical processing efficiency play major roles in the selection of the coordinate reference. Below is a list of criteria which are used in this determination:

    ______________________________________                                         ADS MESSAGE FORMAT CRITERIA DEFINITIONS                                        ______________________________________                                         WORLD WIDE USE  The coordinate reference system is                                             recognized throughout the world. Scale                                         does not change as a function of where                                         you are on the earth.                                          SIMPLE NAVIGATION                                                                              The coordinate system lends itself to                          MATHEMATICS     simple vector navigational mathematics.                        COMPATIBLE WITH The coordinate reference can support                           COMPLEX 4-D CURVED                                                                             curved trajectory mathematics.                                 PATH 4-D NAVIGATION                                                            FUNCTIONS                                                                      COMPATIBLE WITH Is compatible with management                                  MANAGEMENT SYSTEM                                                                              operations at ATC and aboard A/Vs.                             COMPATIBLE WITH SPACE                                                                          The coordinate system is compatible                            OPERATIONS      with low earth orbit or space-based                                            operations.                                                    NAD83 AND WGS84 REF.                                                                           The reference system is compatible with                                        NAD 83 and WGS 84                                              SINGLE ORIGIN   The system has one single point origin.                        LINEAR SYSTEM   The system is a linear coordinate system                                       and does not change scale as a function                                        of location.                                                   UNITS OF DISTANCE                                                                              The coordinate system is based on units                                        of distance rather than angle                                  NO DISCONTINUTITIES                                                                            The coordinate reference system is                                             continous world wide.                                          ______________________________________                                    

The ECEF X,Y,Z Cartesian coordinate system satisfies all of the above criteria. Other systems may be used such as, Universal Transverse Mercator, Latitude, Longitude and Mean Sea Level and other grid systems but additional processing overhead and complexities are involved. A representative ADS message structure is provided below:

    ______________________________________                                         SAMPLE AIRPORT ECEF MESSAGE CONTENT                                            ______________________________________                                         ID #                  8 Characters                                             VEHICLE TYPE          4 Characters                                             CURRENT POSITION:                                                              ECEF X Position (M)   10 Characters                                            ECEF Y Position (M)   10 Characters                                            ECEF Z Position (M)   10 Characters                                            ECEF X2 Position (M)  4 Characters *                                           ECEF Y2 Position (M)  4 Characters *                                           ECEF Z2 Position (M)  4 Characters *                                           ECEF X3 Position (M)  4 Characters *                                           ECEF Y3 Position (M)  4 Characters *                                           ECEF Z3 Position (M)  4 Characters *                                           ECEF X Velocity (M/S) 5 Characters                                             ECEF Y Velocity (M/S) 5 Characters                                             ECEF Z Velocity (M/S) 5 Characters                                             NEXT WAYPOINT (WHERE HEADED INFORMATION):                                      ECEF X                10 Characters                                            ECEF Y                10 Characters                                            ECEF Z                10 Characters                                            TIME                  8 Characters                                             ______________________________________                                    

A bit oriented protocol, representing the same type of information, may be used to streamline operations and potential error correction processing. (The asterisks denote optional fields which may be used to determine the attitude of an aircraft.)

The individual fields of the ADS message are described below.

ID (8 CHARACTER WORD, ALPHA-NUMERIC)

The ID field is used to identify the particular vehicle or aircraft. For aircraft this is typically the flight number or, in the case of GA or private aircraft, the tail number. For airport surface vehicles it is the vehicle's callsign.

TYPE OF VEHICLE (4 CHARACTER WORD, ALPHA-NUMERIC)

The vehicle type is used to identify the A/V's type classification. Numerous type classifications may be defined to categorize and identify various aircraft and surface vehicles.

CURRENT ECEF X,Y,Z POSITION (10 CHARACTERS BY 3 WORDS)

The ECEF X,Y,Z position fields provide the vehicle's position at the time of the ADS transmission in ECEF X,Y,Z coordinates. The position is calculated by the GPS receiver. Based on the system design, these values may or may not be smoothed to compensate for system latencies. The message length of 10 characters provides a sign bit in the most significant digit and 9 digits of positional accuracy. The least significant digit represents 0.1 meter resolution. This provides a maximum ADS distance of +9999999.9 which translates to an altitude of about 3600 KM above the earth's surface, providing sufficient coverage to support low earth orbiting satellites and spacecraft.

DELTA POSITIONS (RELATIVE POSITIONS, 4 CHARACTERS BY 6 WORDS)

Delta positions are used to represent the positional offset of two other GPS antenna locations. These locations can be used to determine the altitude of the aircraft or its orientation when it is not moving. All delta distances are calculated with respect to the current ECEF position. Straight forward ECEF vector processing may then be used to determine the attitude and orientation of the aircraft with respect to the ECEF coordinate frame. An ECEF-to-local on board coordinate system (ie. North, East, Up) conversion may be performed if necessary. Accurate cross wind information can be determined on the ground and on board the aircraft from delta position information. Delta positions may also be used as 3-D graphical handles for map display presentations.

The message length of 4 characters provides a sign bit in the most significant digit and 3 digits of delta position accuracy. The least significant digit represents 0.1 meter resolution.

ECEF X,Y,Z VELOCITY (5 CHARACTERS BY 3 WORDS)

The fields represent the A/V's, ECEF X,Y,Z velocity in meters per second. Tenth of a meter/second resolution is required during the ground phase of GPS based movement detection, latency compensation, zone and collision detection processing.

The message length of 5 characters provides a sign bit in the most significant digit and 4 digits of velocity accuracy.

NEXT WAYPOINT (10 CHARACTERS BY 3 WORDS)

These fields describe where the A/A is currently headed, in terms of the ECEF X,Y,Z coordinates of the next waypoint. This provides intent information which is vital to the collision avoidance functions.

TIME (UNIVERSAL COORDINATED TIME) 8 CHARACTERS

This field identifies the Universal Coordinated Time at the time of the ADS transmission. This time is the GPS derived UTC time (in seconds) plus any latency due to processing delays (optional).

The ADS message format provides a very valuable set of information that simplifies mathematical processing. Since the ECEF cartesian coordinate frame is native to every GPS receiver, no additional GPS burden is incurred. This type of ADS broadcast message information is more than adequate for precision ground and air operations as well as for general ATC/airport control and management functions.

OVERVIEW OF CANDIDATE ADS ARCHITECTURES

Many communication technologies are available which can provide ADS capability. Many of the systems already exist in some form today, but may require modification to meet the requirements of ADS in the terminal area. In evaluating datalink candidates, it is important that future airport standards are not compromised by forcing compatibility with the past. Systems should develop independently in a manner designed to achieve the systems' maximum operational benefits. Transitional elements and issues of compatibility with current systems are better handled through the implementation of translators which do not detect form a future system's true potential.

MODE S INTERROGATION

The Mode S system is in use today and is compatible with today's en route radar and Terminal Radar Approach Control (TRACON)-based air traffic control systems. Current Mode S 1030 MHZ interrogation is performed using Mode S radars which scan at the 4.8 second rate. The scan rate represents the rotational period of the scanning antenna. When a target is interrogated by the radar pulse, the aircraft or vehicle broadcasts its GPS-based information to air traffic control at 1090 MHZ. In this manner, ADS information is received by ATC and by other interrogating sources.

Numerous problems exist with any interrogation technique which has multiple interrogators. For radar systems to provide seamless coverage, surface, parallel runway and airport surveillance radars are required. Aircraft and surface vehicles would require the use of a transponder which broadcasts a response at 1090 MHZ when interrogated at 1030 MHZ. In an environment where multiple interrogations are required, system complexities increase dramatically. Early ATCRBS, Mode A and Mode C systems were troubled with too many unsynchronized interrogation requests. This resulted in cross talk, garble and loss of transmission bandwidth. Further complicating the airport environment is the possibility of reflected signals which interrogate areas of the airport outside the view of the surveillance radar. This clogs the 1090 channel and further complicates surveillance processing. Airborne Mode S transponder operation requires that squitter messages be broadcast when in the air and turned off on the ground. A Mode S squitter is a periodic repetitive broadcast of ADS information. This, by definition, will interfere with airport interrogation broadcasts and essentially create a self jamming system.

Any airport ADS system utilizing a Mode S interrogation capability would require almost a ground up development effort encompassing the myriad of necessary surveillance systems.

MODE S SQUITTER (GPS SQUITTER)

Similarly, the Mode S squitter utilizes the Mode S frequencies. A squitter is a randomly timed broadcast which is rebroadcast periodically. The Mode S squitter broadcasts GPS information at a periodic rate at 1090 MHZ with a bit rate of 1 MBPS. Current thinking requires that the ADS system be compatible with the Traffic Collision Avoidance System (TCAS). The TCAS system currently uses a 56 bit squitter message that must be turned off in the low altitude airport environment since it will interfere with other radar processing activities performed on the ground. Turning TCAS off inside the terminal area (where most midair problems and airport surface collisions occur) defeats the system's operational benefits where they are needed most. Operationally this is unacceptable.

A modified 112 bit squitter message has been proposed by MIT Lincoln Laboratories. With this approach, the GPS data is squittered twice per second to support ground and low altitude operations. The proposed Mode S squitter operation has distinct advantages over the Mode S interrogation method. Broadcasts are generated from all aircraft and )potentially) surface vehicles. Message collisions are possible, especially when the number of users is increased. If a collision occurs, the current message is lost and one must wait for the next message to be transmitted. At a two hertz transmission rate, this is not a significant problem. Analysis performed by MIT Lincoln Laboratories indicates that an enhanced Mode S squitter has potential to support operations at major airports.

The integration of the Mode S Squitter, as currently defined, is not without risk. This implementation requires a fleet update to convert to the 112 bit fixed format. Procedural issues of the switch-over between the 56 and 112 bit operation remain problematic. Operation in metroplex areas such as New York may create operationally dangerous conditions. Airside TCAS and ASR 56 bit transponder responses would be turned off based on phase of flight to be compatible with 112 bit squitter messages used at low altitudes and on the ground. In metroplex areas, confusion is almost certain for both the pilot and air traffic controller when systems are turned off and on. Further modifications may be required to ground and vehicular equipment should these issues be a significant problem.

The 112 bit fixed squitter length message, as defined in May 1994, fails to take advantage of precise GNSS velocity information. This is a significant limiting factor in the proposed squitter message format. The current squitter message is designed to be compatible with today's radar processing software and is not designed to fully capitalize on GNSS and ADS capabilities.

AVIATION PACKET RADIO (AVPAC)

AVPAC radio is currently in use with services provided by ARINC and may be a viable candidate to provide ADS services. Again, a GPS-based squitter or an interrogator-initiated broadcast is utilized at aeronautical VHF frequencies. Work is underway to adapt AVPAC to support both voice and data transmissions. A Carrier Sense Multiple Access (CSMA) protocol is utilized on multiple VHF frequencies.

AIRCRAFT COMMUNICATIONS ADDRESSING & REPORTING SYSTEM

Another communication system currently in use by the aviation industry is ACARS. ACARS is a character oriented protocol and currently transmits at 2400 baud. Work is underway to increase the baud rate to support more complex message formats.

VHF/UHF TIME DIVISION MULTIPLE ACCESS (TDMA)

An interesting communication scheme currently under test and development in Sweden utilizes TDMA operation. TDMA is similar to communication technologies used by the United States military and others. In this system, each user is assigned a slot time in which to broadcast the ADS message. A single or multiple frequency system may be utilized based upon total traffic in the area. Upon entering an airport area, the user equipment listens to all slot traffic. The user equipment then selects an unused broadcast time slot. Precise GPS time is used to determine the precise slot. ADS broadcasts are then transmitted at a periodic rate. Broadcasts typically repeat at one second intervals. Should a collision be detected upon entering a new location, the system then transmits on another clear time slot. Since all time slots are continuously received and monitored, all necessary information for situational awareness and collision avoidance is available.

This system maximizes the efficiency of the broadcast link since, in a steady state environment, no transmission collisions can occur. A time guard band is required to assure that starting and ending transmissions do not overlap. The size of the guard band is a function of GPS time accuracy and propagation delay effects between various users of the system. Another feature of this system is an auto-ranging function to the received broadcasts. This is possible due to the fact that the ADS slot transmissions are defined to occur at precise time intervals. It is then possible, using a GNSS synchronized precise time source, to determine the transit time of the ADS broadcast. By multiplying the speed of light by the transit time, one may calculate the 1-dimensional range to the transmitting object. In reality, a more precise direction, distance and predicted future location is obtainable from the ADS message information itself.

CODE DIVISION MULTIPLE ACCESS (CDMA) SPREAD SPECTRUM

CDMA spread spectrum ADS broadcasts utilize a transmission format similar to that used in the GPS satellites. PRN codes are utilized to uniquely identify the sending message from other messages. The number of users able to simultaneously utilize an existing channel depends upon the PRN codes used and the resulting cross correlation function between the codes. This implementation is being utilized commercially in wireless computer systems with data rates exceeding 256 KBPS. In a frequency agile environment, this implementation may be able to provide secure ADS services.

CELLULAR TELEPHONE

Cellular technology is rapidly changing to support the large potential markets of mobile offices and personal communication systems. CCITT and ISDN standards will provide both voice, video and data capability. Cellular communication may be used by surface vehicles and aircraft for full duplex data link operations. ADS broadcast message formats receivable by ATC and other users will require changes to commercially available services. Cellular telephone has the mass market advantage of cost effective large scale integration and millions of users to amortize development costs over. This particular technology holds promise, and bears watching.

As the above examples show, a number of datalinks exist or may be modified to provide ADS services. It is not the intent of this specification to rigidly define a particular datalink.

ADS OPERATIONAL CONSIDERATIONS

To fully exploit the ADS concepts presented in this specification, a new set of operational procedures and processing techniques are necessary. The ADS concept will provide the controller and the Aircraft/Vehicle (A/V) operator with the best possible view of the airport environment. With highly accurate 3-D position and velocity information, many new operational capabilities are possible which will provide increased efficiency and safety improvements. The following sections show how precise ADS information is used in seamless airport control and management.

DEFINITION OF COMPATIBLE WAYPOINTS

Waypoints based upon the precise 3-D map and standard surface, approach and departure paths are used for surface and air navigation in the 3-D airport space envelope. Waypoints may be stored in a variety of coordinate systems, such as conventional Latitude, Longitude, Mean Sea Level; State Plane Coordinates; ECEF X,Y,Z; and others. The navigational waypoint and on/off course determinations are preferred to be performed in an ECEF X,Y,Z coordinate frame, but this is not mandatory.

Waypoints and navigation processing should be defined and designed for compatibility with air and ground operations, including precision approach capability. The same information and processing techniques should be in place on board the A/V's and at the AC&M. The AC&M performs mirrored navigational processing using the same coordinate references and waypoints as those on board the A/Vs. In this manner, the AC&M system can quickly detect off course and `wrong way` conditions anywhere in the 3-D airport space envelope at the same time these conditions are detected on board the A/V's.

WAYPOINT NAVIGATION MATHEMATICS

The following mathematical example is provided to show how waypoints and trajectories are processed in the ECEF X,Y,Z coordinate reference frame. An actual DGPS flight trajectory is used for this mathematical analysis. The flight trajectory and waypoints have been previously converted to an ECEF X,Y,Z format.

FIG. 11 presented in the earlier ON Or OFF Course Processing section depicts the major ECEF waypoint elements which are used throughout the following navigation mathematical processing example.

The following example utilizes an ECEF Waypoint Matrix. In this example, the next waypoint (NWP) is element 5 in the matrix and the previous waypoint (PWP) is element 4. The values for the waypoints are shown in the examples. The range to the waypoint is determined from the current position. The range is compared to the previous range for possible off course or wrong way conditions. If the range is increasing, the waypoint auto-indexing distance may have been exceeded even though the vehicle is on course. In this situation, the waypoint index is temporarily indexed and checking is performed to determine whether the velocity vector is pointing within X degrees of the next waypoint (in this example it is set to +/-90 degrees). Based upon the outcome, a wrong way signal is generated or the waypoints are indexed. The ECEF cross track vector (XTRK) is determined and projected on to the vertical axis, local lateral axis and the plane tangent with the earth's surface at the current position.

    __________________________________________________________________________     CONSTRUCT TRAJECTORY VECTOR                                                                       INDEX TO NEXT WAYPOINT                                      OF PRESENT POSITION (PP)                                                        ##STR36##         i := 1                                                      PRESENT POSITION   WAYPOINT INDEX                                               ##STR37##                                                                                         ##STR38##                                                   ##STR39##                                                                     WAYPOINT MATRIX Q                                                              WAYPOINT INDICES                                                               PREVIOUS           NEXT                                                        pwp := wpin.sub.1  nwp := wpin.sub.1 + 1                                       pwp = 4            nwp = 5                                                     PREVIOUS WAYPOINT                                                                    PWP := (WP.sub.pwp,0 WP.sub.pwp,1 WP.sub.pwp,2)                                              ##STR40##                                                  NEXT WAYPOINT                                                                        NWP := (WP.sub.nwp,0 WP.sub.nwp,1 WP.sub.nwp,2)                                              ##STR41##                                                  DEFINE VECTOR BETWEEN WAYPOINTS FOR CURRENT TRAJECTORY TIME                          BWP := NWP.sup.T - PWP.sup.T                                                                 ##STR42##                                                  DISTANCE BETWEEN THE WAYPOINTS                                                 | BWP | = 758.2006572307                                     DEFINE VECTOR BETWEEN PRESENT POSITION & NEXT WAYPOINT                               TNWP := NWP.sup.T - PP.sup.<t>                                                               ##STR43##                                                  DISTANCE TO THE WAYPOINT (RANGE)                                               | TNWP | = 367.019470009                                     CHECK RANGE TO SEE IF A WAYPOINT HAS BEEN MISSED                               IF VEH. N RANGE > PREVIOUS VEH. N RANGE THEN                                   PERFORM TEST:                                                                  INCREMENT WAYPOINT INDEX                                                       FIND THE VECTOR LINE BETWEEN THE CURRENT POSITION AND                          NEXT WAYPOINT                                                                  TNWP = NWP(X,Y,Z) - PP(X,Y,Z)                                                  CALCULATE ECEF CURRENT POSITIONS VELOCITY VECTOR                               VEL = (VX, VY, VZ)                                                             CALCULATE DOT PRODUCT BETWEEN THE VELOCITY VECTOR AND TNWP                     COS θ = TNWP(X, Y, Z) dot VEL(VX, VY, VZ)                                |TNWP| = SRT[(X*X) + (Y*Y) + (Z*Z)]                          |VEL| = SRT[(VX*VX) + (VY*VY) + VZ*VZ)]                      COS θ = [(X*VX) + (Y*VY) + (Z*VZ)]/(|TNWP|*.vertli     ne.VEL|)                                                              IF 0 < COS θ < 1                                                                   THEN KEEP CURRENT WAYPT INDEX,                                                 MISSED AUTO WAYPOINT INDEX DISTANCE                                  IF -1 < COS θ <= 0                                                                 THEN GO BACK TO PREVIOUS WAYPOINT                                              FLASH WRONG WAY                                                      PRESENT POSITION NEXT WAYPOINT                                                  ##STR44##                                                                                       ##STR45##                                                    UNIT VECTOR PERPENDICULAR                                                                       UNIT NORMAL FROM DESIRED TRACK                                TO PLANE CONTAINING INTER-                                                                      TO THE PRESENT POSITION POINT                                 SECTING LINES TNWP & LINE                                                      BETWEEN WAYPOINTS                                                               ##STR46##                                                                                       ##STR47##                                                     ##STR48##                                                                                       ##STR49##                                                    CROSS TRACK ERROR CALCULATIONS                                                 CROSS TRACK MAGNITUDE DETERMINATION                                            XTRK := UN · TNWP                                                                      XTRK = 16.7573345255                                          CROSS TRACK VECTOR DETERMINATION                                               VXTRK := UN · XTRK                                                                     VXTRK = -8.0728483774                                         DETERMINE THE ADJUSTED POSITION                                                The adjusted position is the point, on the line between the previous and       next waypoint                                                                  which is normal to the present position.                                             ADJ.sup.<t>  := PP.sup.<t>  + VXTRK                                                        ##STR50##                                                    DETERMINE THE UNIT VECTOR IN THE DIRECTION FROM CENTER OF MASS                 OF THE EARTH TO ADJUSTED POSITION                                              This vector is in the local vertical direction and for all practical           purposes in the vertical                                                       direction at the actual user position, since the separations are very          small compared to the                                                          length of the vector.                                                           ##STR51##                                                                                       ##STR52##                                                    FIND THE PROJECTION OF THE XTRACK VECTOR ON TO THE UNIT VECTOR                 This distance represents the vertical distance to true course                  VERTDIST := VXTRK · UVADJ                                                              VERTDIST = -4.2570109135                                      FIND THE LATERAL AXIS OF XTRK INFORMATION                                      The lateral axis represents horizontal distance to true course from the        current position                                                               A number of steps are necessary in this determination and are outlined         below.                                                                         FIRST FIND THE VECTOR PERPENDICULAR TO THE PLANE FORMED                        BY THE XTRK AND THE UVADJ VECTOR                                                ##STR53##                                                                                       ##STR54##                                                    FIND THE VECTOR (VLAT) WHICH LIES IN THE PLANE FORMED BY                       UVADJ AND VXTRK WHICH IS PERPENDICULAR TO THE UVADJ VECTOR                     IT IS KNOWN THAT VLAT DOT UVADJ = 0 AND UVPER DOT VLAT = 0                     SOLVE FOR VLAT BY USING SIMULTANEOUS EQUATIONS                                 EQUATION #1                                                                    UVADJ.sub.0 VLAT.sub.0 + UVADJ.sub.1 VLAT.sub.1 + UVADJ.sub.2 VLAT.sub.2       = 0                                                                            EQUATION #2                                                                    UVPER.sub.0 VLAT.sub.0 + UVPER.sub.1 VLAT.sub.1 + UVPER.sub.2 VLAT.sub.2       = 0                                                                            SUBSTITUTE AND SOLVE IN TERMS OF VLAT.sub.2                                     ##STR55##                                                                                       ##STR56##                                                    DEFINE VARIABLES FOR EQUATION SUBSTITUTION                                      ##STR57##                                                                      ##STR58##                                                                     DEFINE VLAT VECTOR                                                             NOTE: VLAT(Z) TERM WILL CANCEL OUT WHEN FINDING UNIT VECTOR                    VLAT := (VLATX VLATY 1)   VLAT = (0.989509706 1.3079658867 1)                  DETERMINE THE LOCAL LATERAL AXIS UNIT VECTOR                                    ##STR59##                                                                                         ##STR60##                                                  PERFORM CHECK TO SEE IF UVLAT IS PERPENDICULAR TO UVADJ                        UVADJ · UVLAT.sup.T = 5.5511151231 · 10.sup.-17              CLOSE ENOUGH TO ZERO                                                           IS PERPENDICULAR                                                               PERFORM CHECK TO SEE IF UVLAT IS PERPENDICULAR TO UVPER                        UVPER · UVLAT.sup.T = 0                                               IT IS PERPENDICULAR                                                            PROJECT THE CROSS TRACK TO THE LATERAL AXIS                                    LATDIST := VXTRK · UVLAT.sup.T                                        LATDIST =-16.2075944693                                                                          VERTDIST = -4.2570109135                                     The sign of the lateral distance (LATDIST) and vertical distance               (VERTDIST)                                                                     determine whether one turns right or left or goes up or down to true           course                                                                         __________________________________________________________________________

From a simplicity standpoint, the ECEF coordinate frame provides direct GPS compatibility with minimal processing overhead. The system is based upon the ECEF world wide coordinate frame and provides for 4-D gate-to-gate navigation without local coordinate reference complications. Furthermore, it is directly compatible with zone processing functions as described in earlier sections.

The above techniques can also be expanded to include curved approaches using cubic splines to smooth the transitions between waypoints. A curved trajectory requires changes to the above set of equations. Using cubic splines, one can calculate three cubic equations which describe smooth (continuous first and second derivatives) curves through the 3-D ECEF waypoints. Additional information on the use of splines may be found in mathematical and numerical programming text books. Four dimensional capability is possible when the set of cubic equations is converted into a set of parametric equations in time.

DISPLAY GRAPHICS AND COORDINATED REFERENCES

Three dimensional display graphics, merged with GPS sensor inputs, provide exciting new tools for airport navigation, control and management. Today's airport users operate in a 4-dimensional environment as precisely scheduled operations become increasingly important in an expansion-constrained aviation system. The 4-D capability of GPS integrated with precise 3-D airport maps and computer graphics, provide seamless airport safety and capacity enhancements. The merger of these technologies provides precise, real-time, 3-D situational awareness capability to both the A/V operators and the air traffic controller.

The FIG. 17 shows a missed approach 81 on runway 35 followed by a touch and go 82 on runway 24 at the Manchester Airport. The power of such a situation display 83 presentation for the air traffic controller can be instantly recognized. Upon closer inspection, it becomes increasingly clear that GPS and precise graphical maps can be a valuable asset in air and ground navigation.

For the air traffic controller, 3-D situational awareness displays, supplemented with navigation status information, are sufficient. For the pilot navigating in a 3-D world, a 3-D terrain or airport map superimposed with graphical navigational information would be extremely valuable, particularly in adverse weather conditions.

The FIG. 18 combines the elements of precise ECEF navigational information with a 3-D airport map. The key element in the construction of the map is compatibility with the navigation display, where the selection of map and navigation coordinate frames is of paramount importance. Upon inspection of computer graphical rotation and translational matrices, it becomes clear that, for processing speed and mathematical efficiency, the Cartesian coordinate system is preferred for the map database. A 3-D, X,Y,Z digital map presentation provides the most efficient path to 2-D screen coordinates through the use of projection transformations.

The integration of GPS-based navigation information with digital maps suggests that new methods of navigation processing should be considered. In the past, aircraft typically relied on a signal in space for instrument-based navigation. The instrument landing system (ILS) consists of a localized directed signal of azimuth and elevation. The VOR-DME navigation system uses a signal in space which radiates from an antenna located at a particular latitude and longitude. Altitude is determined from pressure altitude. Current, 2-D radar surveillance systems are also based upon a localized coordinate reference, usually to the center of the radar antenna. Again, altitude information is from barometric pressure readings which vary with weather. The integration of localized navigation and surveillance systems and 3-D ATC and navigational display presentations require an excessive number of coordinate conversions, making the process overly difficult and inaccurate.

To minimize navigational and display overhead, a Cartesian X,Y,Z coordinate system is used for the navigation computations, map database and display presentations. Many X,Y,Z map database formats are in use today, but many are generated as a 2-D projection with altitude measured above mean sea level. Two examples of this type of system are Universal Transverse Mercator (UTM) and State Plane Coordinate System (SPCS). Neither one of these systems is continuous around the world, each suffer from discontinuities and scale deformity. Furthermore, neither of these systems is directly compatible with GPS and also requires coordinate conversions. If the map, travel path waypoints, navigational processing, navigational screen graphics and airport control and management functions are in the Cartesian coordinate frame, the overall processing is greatly simplified.

In the graphical navigation display FIG. 18, the perspective is that of a pilot from behind his current GPS position 84. From this vantage point 85, the pilot can view his current position 84 and his planned travel path 86. As the aircraft moves, its precise ECEF X,Y,Z velocity 87 components are used to determine how far back 88 and in what direction the observation is conducted from. This is determined by taking the current ECEF velocity 87, negating it and multiplying it by a programmable time value (step-back time). When applied to the aircraft's current position 84, this results in an observation point 89 which is always looking at the current position 84 and ahead in the direction of travel 87.

Once the observation point 89 is established in the 3-D Cartesian coordinate system, an imaginary mathematical focal plan 90 is established containing the current position 84. The focal plane 90 is orthogonal to the GPS-derived ECEF velocity vector 87. The mathematical focal plane 90 represents the imaginary surface where the navigation `insert` 91 will be presented. The focal plane is always, by definition, orthogonal to the viewing point 85. The travel path 86 composed of ECEF X,Y,Z waypoints (92-95) is drawn into the 3-dimensional map. The point on the true travel path 86 which is perpendicular to the current position 84 represents the center 96 of the navigational insert screen 91. The orientation of the navigational insert with respect to the horizontal axis is determined by the roll of the aircraft. The roll may be determined through the use of multiple GPS antennas located at known points on the aircraft or may be determined by inertial sensors and then converted to the ECEF coordinate frame. Vector mathematics performed in the ECEF coordinate frame are then used to determine the new rotated coordinates of the navigation screen insert 91. The rotated coordinates are then translated through the use of the graphical translation matrix and drawn into the 3-D map 97.

The final step is the placement of the current position `cross-hair` symbol 84 with respect to travel path 86. The aircraft's GPS position, previous and next waypoints are used to determine the ECEF cross track vector 98. The cross track vector 98 is then broken down into its local vertical 99 and local lateral 100 (horizontal) components. (Local components must be used here since the vertical and lateral vectors change as a function of location on the earth.) The cross-hair symbol 101 is then drawn on to the focal (image) plane 90 surface at the proper offset from the true course position indicated by the center of the navigation screen insert 96. Thus, this display provides precise navigation information (lateral and vertical distance to true course) with respect to true course, provides information on 3-D airport features and shows the planned 3-D travel path. The element of time may also be presented in this display format as an arrow (drawn in the direction of travel) of variable length where the length indicates speed up or slow down information.

The construction of this type of display in other than ECEF coordinates entails substantial coordinate conversion and additional processing. Again, for simplicity and compatibility with proven 3-dimensional graphic techniques, an ECEF Cartesian X,Y,Z coordinate framework is desired.

GPS NAVIGATOR DISPLAY

Various display formats are used to provide the GPS navigational information to the pilot. The area navigation display shown in FIG. 19 features auto-scaling range 102 rings 103 which provide course, 104 bearing 105 and range distance to the waypoint. The length of the course 104 and bearing lines 105 superimposed on the ring scale 103 are proportional to the distance from the waypoint. The compass orientation of the bearing line 105 provide the course to travel from the current position to the waypoint. The course line 104 indicates the compass direction of current travel. The display also provides altitude information as a auto-scaling bar chart display 106 with indicated go up or down information.

In this manner the area navigation display provides the following:

1. Range to the waypoint based on length of the line and an autoranging scale

2. Compass heading to travel to the waypoint

3. Compass heading of current travel

4. Autoranging altitude navigation bar graph display

The GPS landing display is shown in FIG. 20. This display is activated when the first GPS waypoint at the top of the glide slope is reached. The precision landing display is composed of a simple heavy cross 107 which moved about on an XY graticuled cross hair display 108. Textual TURN LEFT/TURN RIGHT and GO UP/GO DOWN messages are presented to the pilot when the aircraft is more than a predetermined amount e.g. 100 meters off of true course.

Another display format utilizing a 3-D map is provided in FIG. 21. This display technique provides a 3-D view of the approaching airport as viewed from the aircraft's position. The techniques described above for the cross hair navigation screen are identical to those used in the 3-D approach presentation. In the 3-D approach presentation, a concial zone 109 is constructed around the line 110 between the landing approach waypoints. The apex of the cone is at the touch down point 111 and the base of the cone is at the top of the glide slope waypoint. This 3-D object is viewed normal to the line between the current and previous waypoint as shown in FIG. 21.

The cone is sliced at the point on the line (formed by the current and previous waypoint) perpendicular to the present position 112. The resulting cross section then effectively represents the cross hair symbology implemented in the graphical GPS landing display. The current position is then displayed within the conical cross section 113 of the glide slope zone 109. A position not in the center of the display means the aircraft is not on true course. For example, a position report in the upper right of the display cross section means the aircraft is too high and too far to the right. In this case the pilot should turn left and go down. As the aircraft gets closer to the touch down point, the concial cross section scale gets smaller. Once the touchdown waypoint 114 is reached, the display reverts to a plan view of the airport similar to that shown in FIG. 8 which is then used for surface navigation. The graphical nature of this display format is useful in the air and on the ground, but requires very fast graphical and computational performance. The advantage of this system is that it minimizes many of the navigational calculations such as cross track errors, but requires moderate spatial graphical computations and fast display performance. ##SPC3##

AC&M SUBSYSTEMS

COMMUNICATIONS PROCESSOR AND COMMUNICATION FLOW

The processing of data communications within the airport is a key element of any GPS-based airport control and management system. A minimum of three types of messages must be addressed:

(1) the broadcast of Differential GPS correction messages to the vehicles

(2) the transmission and receipt of Automatic Dependent Surveillance (ADS) messages

(3) the transmission of control messages from the AC&M to the vehicle and vice versa.

A high level block diagram of the Airport Communications System and its interfaces to other major elements of the AC&M subsystem is provided in FIG. 22.

In this design, all ADS and A/V messages are received by the AC&M Processor 115 and are forwarded to the COMM Processor 116 for re-transmission to the vehicles. The AC&M Processor is also used to compose ATC messages which are also forwarded to the vehicles through the COMM interface or passed to the local Graphics Processor 117 to control the situation display presentation. The COMM processor 116 also transmits the differential correction messages generated by the reference station 118 directly to the vehicles.

DIFFERENTIAL GPS OVERVIEW

Real time differential correction techniques compensate for a number of error sources inherent to GPS. The idea is simple in concept and basically incorporates two or more GPS receivers, one acting as a stationary base station 118 and the other(s) acting as roving receiver(s) 119, 120. The differential base station is "anchored" at a known point on the earth's surface. The base station receives the satellite signals, determines the errors in the signals and then calculates corrections to remove the errors. The corrections are then broadcast to the roving receivers.

Real time differential processing provides accuracy of 10.0 meters or better (typically 1.0-5.0 meters for local differential corrections). The corrections broadcast by the base station are accurate over an area of about 1500 km or more. Typical positional degradation is approximately a few millimeters of position error per kilometer of base station and roving receiver separation.

Through the implementation of local differential GPS techniques, SA errors are reduced significantly while the atmospheric errors are almost completely removed. Ephemeris and clock errors are virtually removed as well.

ANTENNA PLACEMENT

A site survey of potential differential base station sites should be performed to determine a suitable location for the GPS antenna. The location should have a clear view of the sky and should not be located near potentially reflective surfaces (within about 300 meters). The antenna site should be away from potentially interfering radiation sources such as radio, television, radar and communications transmitters. After a suitable site is determined, a GPS survey should be conducted to determine the precise location of the GPS antenna--preferably to centimeter level accuracy. This should be performed using survey grade GPS equipment.

Survey grade GPS equipment makes use of the 19 and 21 centimeter wavelength of the L1 and L2 GPS transmissions. Real time kinematic or post processing GPS surveys may be conducted. Real time kinematic utilizes a base station located at a precise location which broadcasts carrier phase correction and processing data to a radio receiver and processing computer. Code, carrier integral cycles and carrier phase information are used at the survey site to calculate the WGS 83 antenna position. In the post processing survey mode, subframe information, time, code, carrier, and carrier phase data are collected for a period of time. This data is later post processed using precise ephemerides which are available from a network of international GPS sites. The collected information is then post processed with post-fit precise orbital information.

BASE STATION OPERATIONAL ELEMENTS

The precisely surveyed location of the GPS antenna is programmed into the reference station as part of its initial installation and set up procedures. Industry standard reference stations determine pseudo range and delta range based on carrier smoothed measurements for all satellites in view. Since the exact ECEF position of the antenna is known, corrections may be generated for the pseudo range and delta range measurements and precise time can be calculated.

Naturally occurring errors are, for the most part, slow changing and monotomic over the typical periods of concern. When SA is not invoked, delta range corrections provide a valid method of improving positional accuracy at the roving receivers using less frequent correction broadcasts. With the advent of SA and its random, quick changing non-monotonic characteristics, delta range corrections become somewhat meaningless and may actually degrade the system performance under some conditions.

As shown previously in FIG. 22 the DGPS correction messages are broadcast by the reference station and received by the roving receivers. The corrections are applied directly to the differential GPS receiver. The DGPS receiver calculates the pseudo range and the delta range measurements for each satellite in the usual manner. Prior to performing the navigation solution, the received pseudo range and delta range corrections are applied to the internal measurements. The receiver then calculates corrected position, velocity and time data.

Since differential GPS eliminates most GPS errors, it provides a significant improvements in system reliability for life critical airport operations. Short term and long term drift of the satellite orbits, clocks and naturally occurring phenomenon are compensated for by differential GPS as are other potential GPS satellite failures. Differential GPS is mandatory in the airport environment from a reliability, accuracy and fault compensating perspective.

As with autonomous GPS receiver operation, multipath is a potential problem. The differential reference station cannot correct for multipath errors at the roving receiver(s). Antenna design and placement considerations, and receiver design characteristics remain the best solutions to date in the minimization of multipath effects.

ADS MESSAGES

ADS messages are generated on board each vehicle and broadcast to the AC&M System. The message format is shown below:

    MSG HEADER, VEHICLE ID, VEHICLE TYPE, ECEF X, ECEF Y, ECEF Z, ECEF X VEL, ECEF Y VEL, ECEF Z VEL<CR><LF>

On board each vehicle, the GPS-based position and velocity data is converted to Earth Centered Earth Fixed (ECEF) coordinates for use in the navigation and zone processing algorithms if necessary. For simplicity, this format is used in the ADS transmission as well. Upon receipt of an ADS message, the AC&M Processor 115 forwards the message to the COMM Processor 116 then stores the data in the vehicle database. The stored ECEF position and velocity data is used to perform collision prediction, zone incursion, lighting control and navigation processing at the AC&M station.

ATC MESSAGES

Air Traffic Control (ATC) messages are composed using the AC&M station. The ATC messages are used locally to control the AC&M graphics display 117 or present current status information to the user. ATC message are also broadcast to the vehicles 119 and 120 through the COMM Processor 116. All ATC messages utilize an explicit acknowledgment message. If an acknowledgment is not received within a defined time interval, the message is automatically retransmitted. The standard format is shown below.

    SATC, MESSAGE TYPE, VEHICLE ID, MESSAGE DATA<CR><LF>

ERROR DETECTION AND CORRECTION

In the demonstration prototpye system, Cyclical Redundancy Checking (CRC) is performed on all messages, with the exception of the [RTCM-104] differential correction messages generated in the Base Station 118. In this scheme, ADS messages are discarded if an error is detected in the received message. This has not been a significant problem for the prototype system since the next message is received in one (1.0) second. The ATC messages directed to specific vehicles also support CRC error detection. ATC messages are "addressed" to a specific A/A and expect an explicit acknowledgment. Upon receipt of an ATC message, the A/V sends back a valid "message received" acknowledgment. The ATC message is discarded by the A/V if an error is detected. In this case, no message received acknowledgment is generated. If no "message received" acknowledgment is received by the AC&M 115 within a preset time interval, the original message is immediately retransmitted. ATC messages require a corresponding acknowledgment since they may represent critical controller instructions and airport and safety operations could be compromised if the message fails to reach its destination.

The CRC system operated effectively in the demonstration prototype system, but a more robust communication error detection and correction capability may be required for end state deployment. Forward error correction and Viterbi--Trellis techniques provide a cost effective forward error correction capability. These techniques are widely used in commercial modem technology and are available in application Specific Integrated Circuits (ASIC). Wide spread use of the technology makes it very cost effective for use in future airport communication systems.

AC&M PROCESSOR AND AC&M PROCESSING FLOW

A block diagram of the AC&M Processor is provided in FIG. 23.

The AC&M Processor 121 is based on a 33 MHz 386 processor with a 387 math co-processor. This processor performs the following functions:

Interfaces to communication digital datalinks

Receives ADS vehicle broadcasts

Receives acknowledgment messages from vehicles

Generates and transmits messages to vehicles

Performs collision prediction processing for each vehicle

Monitors zone and runway incursion conditions

Controls runway intersections and runway clearance lights

Maintains and controls vehicle, waypoint and zone data bases

Performs navigational processing for on-off course checking

Performs map layer control and assignment

Sends vehicle reports and commands to Graphic Processor for situation display

Provides a touch screen and keyboard command interface

Representative command functions are described in the following section.

AC&M COMMAND LIST

ARRIVAL WAYPOINTS: The ARRIVAL WAYPOINTS command is issued to grant a landing clearance to an approaching aircraft and provide it with a set of waypoints for the landing operation.

DEPARTURE WAYPOINTS: The DEPARTURE WAYPOINTS command is issued to grant a takeoff clearance to a departing aircraft and provide it with a set of waypoints for the operation.

SURFACE WAYPOINTS: The SURFACE WAYPOINTS command is issued to grant a ground clearance to an aircraft or surface vehicle and provide it with a set of waypoints for the operation.

CLEAR PATH WAYPOINTS The CLEAR PATH WAYPOINTS command is issued to manually end a previously granted clearance and clear any pending waypoints for a specific vehicle

AIRPORT LIGHTS: The AIRPORT LIGHTS command is issued to manually change the status of a specific set of runway approach, departure or intersection lights.

VEHICLE FILTER: The VEHICLE FILTER command is issued to enable or suppress the display of a particular type of vehicle by altering the status of its graphic layer.

LAYER FILTER: The LAYER FILTER command is issued to manually change the status of a specific graphic layer. Layers which are masked are no longer displayed.

    ______________________________________                                         LAYER TYPE                  STATUS                                             ______________________________________                                         RANGE RINGS                 ON                                                 RANGE RINGS, 5 MILE INCREMENTS                                                                             ON                                                 AIRPORT LIGHTING SYSTEMS (RNWY 35)                                                                         OFF                                                AIRPORT LIGHTING SYSTEMS (RNWY 24)                                                                         OFF                                                TRACKED SURFACE VEHICLES (LIMITED ACCESS)                                                                  ON                                                 TRACKED SURFACE VEHICLES (FULL ACCESS)                                                                     ON                                                 TRACKED DEPARTURE AIRCRAFT  ON                                                 TRACKED ARRIVAL AIRCRAFT    ON                                                 ARRIVAL WAYPOINTS           OFF                                                DEPARTURE WAYPOINTS         OFF                                                SURFACE WAYPOINTS           OFF                                                CUSTOM WAYPOINTS DEFINITION OFF                                                AIRPORT SURFACE ZONES       OFF                                                WEIGHT LIMITED ZONES        OFF                                                RESTRICTED TRAVEL AREA      OFF                                                AIRSPACE HAZARD ZONES       OFF                                                OPEN CONSTRUCTION ZONES     OFF                                                CLOSED CONSTRUCTIONS ZONES  OFF                                                ______________________________________                                    

VEHICLE DATA: The VEHICLE DATA command is issued to display status information for a particular vehicle. The vehicle data is displayed in the MC&R window.

DISPLAY VIEW: The DISPLAY VIEW command is issued to change the display view presented on the situation display.

    ______________________________________                                         VIEW ID       DESCRIPTION                                                      ______________________________________                                         00            PLAN VIEW 10 MILE RANGE                                          01            PLAN VIEW 5 MILE RANGE                                           02            PLAN VIEW 1 MILE RANGE                                           03            PLAN VIEW .5 MILE RANGE                                          04            RUNWAY 35                                                        05            RUNWAY 17                                                        06            RUNWAY 24                                                        07            RUNWAY 06                                                        08            GATE AREA                                                        09            FIRE, CRASH AND RESCUE                                           10            TERMINAL BUILDING                                                11            3D VIEW RUNWAY 35                                                12            3D VIEW RUNWAY 17                                                13            3D VIEW RUNWAY 24                                                14            3D VIEW RUNWAY 06                                                15            APPROACH VIEW RUNWAY 35                                          16            APPROACH VIEW RUNWAY 17                                          17            APPROACH VIEW RUNWAY 24                                          18            APPROACH VIEW RUNWAY 06                                          ______________________________________                                    

AIRPORT LIGHTS: The system also demonstrates the capability to control airport lights based on GPS inputs and current clearance status.

    __________________________________________________________________________     RUNWAY 35 LIGHT STATUS                                                                            LANDING                                                                               INTERSECTION                                                                           TAKEOFF                                      ACTIVITY DESCRIPTION                                                                              LIGHTS LIGHTS  LIGHTS                                       __________________________________________________________________________     NO ACTIVITY STATE                                                              (RUNWAY 35)        RED    OFF     RED                                          (RUNWAY 17)        RED    OFF     RED                                          TAKE OFF CLEARANCE GIVEN - 35                                                  (35 - TAKEOFF END) RED    OFF     RED                                          (17 - OPPOSITE END)                                                                               RED    OFF     RED                                          AIRCRAFT ENTERS RNWY 35 ZONE                                                   (35 - TAKEOFF END) RED    RED     GREEN                                        (17 - OPPOSITE END)                                                                               RED    RED     RED                                          TAKE OFF COMPLETED                                                             (35 - TAKEOFF END) RED    OFF     RED                                          (17 - OPPOSITE END)                                                                               RED    OFF     RED                                          LANDING CLEARANCE ISSUED - 35                                                  (35 - APPROACH END)                                                                               GREEN  RED     RED                                          (17 - OPPOSITE END)                                                                               RED    RED     RED                                          ARRIVAL AIRCRAFT EXITS RUNWAY                                                  (RUNWAY 35)        RED    OFF     RED                                          (RUNWAY 17)        RED    OFF     RED                                          RUNWAY INCURSION OCCURRED                                                      (RUNWAY 35)        FLASH  FLASH   FLASH                                                           RED/GREEN                                                                             RED/OFF RED/GREEN                                    (RUNWAY 17)        FLASH  FLASH   FLASH                                                           RED/GREEN                                                                             RED/OFF RED/GREEN                                    RUNWAY INCURSION ENDS                                                          (RUNWAY 35)        RED    OFF     RED                                          (RUNWAY 17)        RED    OFF     RED                                          __________________________________________________________________________

Airport lighting control techniques are provided as a demonstration mechanism and are not intended to dictate a specific lighting scheme for airports.

SITUATION DISPLAY

A vehicle database is maintained by the AC&M and on board `fully equipped` vehicles to provide a situational awareness capability to the controller and/or vehicle operator. GPS-based situational awareness requires the integration of a datalink between the aircraft, surface vehicles and AC&M system. In the demonstration prototype system, the position and velocity information determined on board each vehicle is broadcast over an experimental VHF datalink and received by the AC&M. At the AC&M, the message is assembled into a dynamic vehicle database. As each ADS message is received, the following fields in the vehicle database are updated:

Vehicle I

Vehicle Type

Position (ECEF X,Y,Z)

Velocity (ECEF X,Y,Z)

In order to present the vehicle position data graphically, the following information is also maintained in the vehicle database:

Layer ID

Vehicle Color

Each vehicle is assigned a map layer based on vehicle type. The digital airport map features numerous object oriented layers which are used to segregate various types of graphical information. By assigning vehicles to specific map layers, spatial filtering may be performed on a layer by layer basis. Color may be assigned by layer or by individual vehicle.

Position reporting functions operating on a moving platform potentially suffer from a positional error introduced by processing time. To compensate for this factor, the precise DGPS derived ECEF velocity components are used to project the position ahead. As each ADS message is received, a latency compensation time projection factor is applied in an ECEF Velocity×Time relationship. The new, projected ECEF position is then considered the current position, is stored in the vehicle database and is used throughout the navigation and collision prediction algorithms.

Once the dynamic vehicle database is constructed, a sequential scanning of the database is performed as new ADS position reports are received. Vehicles outside of the defined range are filtered out. Vehicles within range are displayed in the 3-D airport map. In this manner, graphical situational awareness is provided at the AC&M and on board the vehicles/aircraft.

COLLISION PREDICTION PROCESSING

As ADS messages are received, collision prediction processing is performed using the current GPS data and the information stored in the vehicle database. The following database fields are used in the collision prediction processing.

    ______________________________________                                         Collision Time                                                                               Time (secs) when a collision may occur                           Collision Count                                                                              Number of potential collisions detected                          Collision Condition                                                                          Warning or watch state detected                                  Collision Separation                                                                         Current collision separation                                     Radius        Vehicle's minimum separation radius                              ______________________________________                                    

A `rough check` is performed to determine if there are any vehicles in the immediate vicinity of the current vehicle. The current vehicle's position is projected ahead using a defined MAXIMUM₋₋ PROTECTION₋₋ FACTOR. The vehicle database is sequentially scanned. The position of the first vehicle in the database is projected ahead in the same manner. If the projected positions intersect, further collision checking is performed.

When further collision checking is warranted, the current vehicle's position is projected ahead by incrementing time in one second intervals. At each interval, an imaginary sphere is drawn around the vehicle using a predefined radius based on the vehicle's minimum safe separation. Similarly, the position of the next vehicle in the database is projected ahead. If the two imaginary spheres intersect and the time interval of the intersection is less than or equal to the MINIMUM₋₋ WARNING₋₋ TIME factor, a collision warning condition is generated. If the two imaginary spheres intersect at a time interval greater than the MINIMUM₋₋ WARNING₋₋ TIME but less than the MINIMUM₋₋ WATCH₋₋ TIME, a collision watch condition is generated.

If a collision watch condition is generated, the vehicles in the watch condition are displayed in YELLOW on the AC&M map display. A warning message is displayed to the operator in the Alerts window of the touchscreen. If a warning condition is detected, the vehicle's symbol is displayed in RED on the graphics screen and a warning message is displayed in the Alert window.

During any collision condition, the vehicle's symbol is moved to a dedicated watch or warning map layer. These layers are reserved for critical operations and cannot be suppressed by the user.

The following collision data was generated from actual₋₋ collision tests and represents two surface vehicles driving towards each other. During this test scenario, the following factors were used:

    ______________________________________                                         MINIMUM.sub.-- WARNING.sub.-- TIME                                                                     3 seconds                                              MINIMUM.sub.-- WATCH.sub.-- TIME                                                                       7 seconds                                              RADIUS, VEHICLE 03      7 meters                                               RADIUS, VEHICLE 04      7 meters                                               ______________________________________                                    

Note that a COLLISION WATCH is detected when the distance between the two vehicles is less than the sum of its radii. A COLLISION WARNING is detected when the intersection occurs within the MINIMUM₋₋ WARNING₋₋ TIME of 3 seconds or less. Also note that as soon as the vehicles pass one another and the distance between them begins to increase, no WATCH or WARNING condition is detected.

    ______________________________________                                         VEH = 03 DIST = 74.9 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 64.7 PROJ TIME = 2 SECONDS                                     VEH = 03 DIST = 54.5 PROJ TIME = 3 SECONDS                                     VEH = 03 DIST = 44.3 PROJ TIME = 4 SECONDS                                     VEH = 03 DIST = 34.2 PROJ TIME = 5 SECONDS                                     VEH = 03 DIST = 24.0 PROJ TIME = 6 SECONDS                                     VEH = 03 DIST = 14.0 PROJ TIME = 7 SECONDS COLLISION                           WATCH                                                                          VEH = 04 DIST = 70.0 PROJ TIME = 1 SECONDS                                     VEH = 04 DIST = 59.7 PROJ TIME = 2 SECONDS                                     VEH = 04 DIST = 49.5 PROJ TIME = 3 SECONDS                                     VEH = 04 DIST = 39.2 PROJ TIME = 4 SECONDS                                     VEH = 04 DIST = 29.0 PROJ TIME = 5 SECONDS                                     VEH = 04 DIST = 18.8 PROJ TIME = 6 SECONDS                                     VEH = 04 DIST = 8.9 PROJ TIME = 7 SECONDS COLLISION                            WATCH                                                                          VEH = 03 DIST = 64.1 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 53.7 PROJ TIME = 2 SECONDS                                     VEH = 03 DIST = 43.4 PROJ TIME = 3 SECONDS                                     VEH = 03 DIST = 33.1 PROJ TIME = 4 SECONDS                                     VEH = 03 DIST = 22.8 PROJ TIME = 5 SECONDS                                     VEH = 03 DIST = 12.7 PROJ TIME = 6 SECONDS COLLISION                           WATCH                                                                          VEH = 04 DIST = 59.1 PROJ TIME = 1 SECONDS                                     VEH = 04 DIST = 48.6 PROJ TIME = 2 SECONDS                                     VEH = 04 DIST = 38.1 PROJ TIME = 3 SECONDS                                     VEH = 04 DIST = 27.6 PROJ TIME = 4 SECONDS                                     VEH = 04 DIST = 17.1 PROJ TIME = 5 SECONDS                                     VEH = 04 DIST = 7.0 PROJ TIME = 6 SECONDS COLLISION                            WATCH                                                                          VEH = 03 DIST = 53.3 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 42.7 PROJ TIME = 2 SECONDS                                     VEH = 03 DIST = 32.3 PROJ TIME = 3 SECONDS                                     VEH = 03 DIST = 21.8 PROJ TIME = 4 SECONDS                                     VEH = 03 DIST = 11.4 PROJ TIME = 5 SECONDS COLLISION                           WATCH                                                                          VEH = 04 DIST = 47.8 PROJ TIME = 1 SECONDS                                     VEH = 04 DIST = 37.1 PROJ TIME = 2 SECONDS                                     VEH = 04 DIST = 26.4 PROJ TIME = 3 SECONDS                                     VEH = 04 DIST = 15.8 PROJ TIME = 4 SECONDS                                     VEH = 04 DIST = 5.4 PROJ TIME = 5 SECONDS COLLISION                            WATCH                                                                          VEH = 03 DIST = 41.9 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 31.2 PROJ TIME = 2 SECONDS                                     VEH = 03 DIST = 20.5 PROJ TIME = 3 SECONDS                                     VEH = 03 DIST = 9.9 PROJ TIME = 4 SECONDS COLLISION                            WATCH                                                                          VEH = 04 DIST = 36.6 PROJ TIME = 1 SECONDS                                     VEH = 04 DIST = 25.9 PROJ TIME = 2 SECONDS                                     VEH = 04 DIST = 15.3 PROJ TIME = 3 SECONDS                                     VEH = 04 DIST = 5.4 PROJ TIME = 4 SECONDS COLLISION                            WATCH                                                                          VEH = 03 DIST = 31.9 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 21.2 PROJ TIME = 2 SECONDS                                     VEH = 03 DIST = 10.6 PROJ TIME = 3 SECONDS COLLISION                           WARNING                                                                        VEH = 04 DIST = 26.6 PROJ TIME = 1 SECONDS                                     VEH = 04 DIST = 15.9 PROJ TIME = 2 SECONDS                                     VEH = 04 DIST = 5.6 PROJ TIME = 3 SECONDS COLLISION                            WARNING                                                                        VEH = 03 DIST = 14.4 PROJ TIME = 1 SECONDS                                     VEH = 03 DIST = 4.6 PROJ TIME = 2 SECONDS COLLISION                            WARNING                                                                        VEH = 04 DIST = 10.6 PROJ TIME = 1 SECONDS COLLISION                           WARNING                                                                        VEH = 03 DIST = 5.9 PROJ TIME = 1 SECONDS COLLISION                            WARNING                                                                        VEH = 04 DIST = 2.9 PROJ TIME = 1 SECONDS COLLISION                            WARNING                                                                        DIST = 5.4, VEHICLE SEPARATION IS INCREASING, STOP                             PROCESSING . . .                                                               ______________________________________                                    

ZONE INCURSION PROCESSING

A 3-D map database and ECEF mathematical processing algorithms support the concept of zones. Zones are three dimensional shapes which are used to provide spatial cueing for a number of constructs unique to DSDC's demonstration system. Zones may be defined around obstacles which may pose a hazard to navigation, such as transmission towers, tall buildings, and terrain features. Zones may also be keyed to the airport's NOTAMS, identifying areas of the airport which have restricted usage.

Zones are represented graphically on the map display and mathematically by DSDC's zone processing algorithms. Multi-sided zones are stored in a zone database as a series of points. Each zone is assigned a zone id and type. The zone type is used to determine whether a particular zone is off-limits for a specific vehicle type.

Zone information is maintained in the zone database. A zone incursion status field is also maintained for the vehicle in the vehicle database. If the vehicle is currently inside a zone, this field is used to store the zone's id. If the vehicle is not inside a zone, this field is zero (0).

At the AC&M, zone incursion processing is performed in a manner similar to the collision processing described previously. As each vehicle report is received, it is projected ahead by incrementing time up to a MAX₋₋ ZONE₋₋ PROJECTION₋₋ FACTOR. At each interval, the vehicle's projected position is compared to each line of the zone as defined by its endpoints. If the vehicle's position is inside all of the lines comprising the zone and the current projection time is less than the MIN₋₋ ZONE₋₋ WARNING factor, a zone incursion warning is generated. If the vehicle's position is inside the zone and the current projection time is less than the MIN₋₋ ZONE₋₋ WATCH factor but greater than the MIN₋₋ ZONE₋₋ WARNING factor, a zone incursion watch is generated. As in the collision processing, a zone incursion watch or warning will result in a message displayed to the operator and a change in layer assignments for the affected vehicle.

A zone incursion condition is automatically cleared when the vehicle exits the zone. All zones are defined as 3-dimensional entities and may be exited laterally or vertically. Heights may be assigned to `surface` zones individually or collectively. The concepts of 3-dimensional zones is critical to an airport environment to prevent passing aircraft from triggering ground-based zones.

RUNWAY INCURSION PROCESSING

If a zone incursion is detected a further check is performed to determine if the vehicle is entering or inside a runway zone. For Manchester airport, five (5) runway zones have been defined:

    ______________________________________                                         RNWY.sub.-- 35.sub.-- ZONE                                                     RNWY.sub.-- 17.sub.-- ZONE                                                     RNWY.sub.-- 24.sub.-- ZONE                                                     RNWY.sub.-- 06.sub.-- ZONE                                                     RNWY.sub.-- INT.sub.-- ZONE  "RUNWAY INTERSECTION VOLUME"                      ______________________________________                                    

An additional field is maintained in the vehicle database to indicate whether a runway incursion state has been detected. As with the zone incursion field, the runway incursion value is set to the id of the zone (i.e., the runway) if an incursion is currently occurring and is set to zero (0) if there is no runway incursion.

If the vehicle is entering or inside a runway zone and is not cleared for that zone, a runway incursion condition is generated at the AC&M. As in any zone incursion situation, a watch or warning message is displayed in the AC&M Alerts window and the vehicle's symbol is moved to the dedicated watch or warning map layer, changing its color to YELLOW or RED. In addition, the runway incursion results in a status change in the runway's landing, takeoff and intersection lights forcing the lights to flash on the affected (and related) runway(s). The following table describes the lighting states for runway incursions in each of the five runway zones.

    __________________________________________________________________________     RUNWAY INCURSION LIGHT STATES                                                               RNWY 35                                                                               RNWY 17                                                                               RNWY 24                                                                               RNWY 06                                      ACTIVITY DESCRIPTION                                                                        ADI    ADI    ADI    ADI                                          __________________________________________________________________________     INCURSION - RNWY 35                                                                         FLASH  FLASH  NO CHANGE                                                                             NO CHANGE                                    INCURSION ENDS                                                                              DEFAULT                                                                               DEFAULT                                                                               NO CHANGE                                                                             NO CHANGE                                    INCURSION - RNWY 17                                                                         FLASH  FLASH  NO CHANGE                                                                             NO CHANGE                                    INCURSION ENDS                                                                              DEFAULT                                                                               DEFAULT                                                                               NO CHANGE                                                                             NO CHANGE                                    INCURSION - RNWY 24                                                                         NO CHANGE                                                                             NO CHANGE                                                                             FLASH  FLASH                                        INCURSION ENDS                                                                              NO CHANGE                                                                             NO CHANGE                                                                             DEFAULT                                                                               DEFAULT                                      INCURSION - RNWY 06                                                                         NO CHANGE                                                                             NO CHANGE                                                                             FLASH  FLASH                                        INCURSION ENDS                                                                              NO CHANGE                                                                             NO CHANGE                                                                             DEFAULT                                                                               DEFAULT                                      INCUR. - INTERSECTION                                                                       FLASH  FLASH  FLASH  FLASH                                        INCURSION ENDS                                                                              DEFAULT                                                                               DEFAULT                                                                               DEFAULT                                                                               DEFAULT                                      __________________________________________________________________________      KEY:                                                                           A = APPROACH LIGHTS FLASH = RED/GREEN DEFAULT = RED                            D = DEPARTURE LIGHTS FLASH RED/GREEN DEFAULT RED                               I = INTERSECTION LIGHTS FLASH = RED/OFF DEFAULT = OFF                    

A runway incursion is automatically terminated when the incurring vehicle exits the runway. When the incursion condition is terminated, the lights on the affected runway return to their default state. As in all zone definitions, runway zones are 3-dimensional entities. Runway zones are assigned a height of approximately 100 meters above the surface of the runway in the prototype demonstration system. Therefor, a runway incursion occurs only when an uncleared vehicle enters the zone at the surface level. Demonstration prototype lighting software is provided below:

LIGHTING CONTROL SOFTWARE EXAMPLE

    ______________________________________                                         /******************************************************                        LIGHTS.H                                                                       Description: lights.h contains the global constants and data structures        for the airport lights.                                                        ******************************************************/                        #define LIGHT.sub.-- ADDR 0x300 /* address of digital IO board */              /*- light bit settings, digital I/O card -*/                                   #define LANDING.sub.-- 35 0x01                                                 #define LANDING.sub.-- 17 0x02                                                 #define LANDING.sub.-- 24 0x04                                                 #define LANDING.sub.-- 06 0x08                                                 #define TAKEOFF.sub.-- 17 0x10                                                 #define TAKEOFF.sub.-- 06 0x20                                                 #define TAKEOFF.sub.-- 35 0x40                                                 #define TAKEOFF.sub.-- 24 0x80                                                 /*----- light status states -----*/                                            #define NO.sub.-- ACTIVITY  0                                                  #define RUNWAY.sub.-- INCURSION 1                                              #define LANDING                                                                           2                                                                   #define TAKEOFF                                                                           3                                                                   #define SURFACE                                                                           5                                                                   /*---- ruwnay id ----*/                                                        #define RNWY.sub.-- 35 35                                                      #define RNWY.sub.-- 17 17                                                      #define RNWY.sub.-- 24 24                                                      #define RNWY.sub.-- 06 6                                                       #define RNWY.sub.-- INT 1                                                      /***********************************************************                   File Name : LIGHTS.C                                                           Description : lights.c contains the procedures used update the airport         lighs                                                                          Units                                                                               : initialize.sub.-- lights,                                                    update.sub.-- lights,                                                          update.sub.-- clearance.sub.-- lights,                                         get.sub.-- runway.sub.-- clear,                                                process.sub.-- clearance                                                  ***********************************************************/                   #include <stdio.h>                                                                        /* standard input/output                                                                       */                                                  #include <graph.h>                                                                        /* MSC graphics routines                                                                       */                                                  #include <string.h>                                                                       /* MSC string routines                                                                         */                                                  #include <stdlib.h>                                                                       /* MSC standard library                                                                        */                                                  #include <math.h>                                                                         /* MSC math library                                                                            */                                                  #include "sio.h"                                                                          /* serial input/output                                                                         */                                                  #include "lights.h"                                                                       /* airport light definitions                                                                   */                                                  #include "veh.h"                                                                          /* vehicle data */                                                  #include "coor.h"                                                                         /* coordinate data                                                                             */                                                  /*------------------- external function -------------------*/                  void store.sub.-- wps(char wp.sub.-- id[12],int wpindex);                      /*------------------- external variables -------------------*/                 extern VEHICLE.sub.-- DATA veh[MAX.sub.-- VEHS]; /* vehicle database */        extern unsigned curr.sub.-- lights: /* current light settings */               /*------------------- global variables -------------------*/                   short current.sub.-- clearance;                                                             /* set if any vehicle is cleared */                               char veh.sub.-- cleared[8];                                                                 /* vehicle cleared for landing/takeoff*/                          short veh.sub.-- clear.sub.-- status;                                                       /* clearance status for curr vehicle */                           short end.sub.-- of.sub.-- wps;                                                             /* end of clearance/wps  */                                       /*------------------------------------------------------------                 UNIT: initialize.sub.-- lights( )                                              DESCRIPTION: initialize.sub.-- lights sets the airport lights to their         default                                                                        settings - RED for landing and takeoff lights and OFF for runway               intersection (i.e., stop) lights.                                              */                                                                             initialize.sub.-- lights( )                                                    update.sub.-- lights(NO.sub.-- ACTIVITY,RNWY.sub.-- 35);                       update.sub.-- lights(NO.sub.-- ACTIVITY,RNWY.sub.-- 17);                       update.sub.-- lights(NO.sub.-- ACTIVITY,RNWY.sub.-- 24);                       update.sub.-- lights(NO.sub.-- ACTIVITY,RNWY.sub.-- 06);                       }                                                                              /*------------------------------------------------------------                 UNIT: update.sub.-- lights                                                     DESCRIPTION: this routine resets the lights on the specified runway            based.                                                                         */                                                                             update.sub.-- lights(int activity.sub.-- type, int rnwy)                       {                                                                              switch (rnwy)                                                                  {                                                                              case RNWY.sub.-- 35 : case RNWY.sub.-- 17 :                                    switch (activity.sub.-- type)                                                  {                                                                              case NO.sub.-- ACTIVITY :                                                             curr.sub.-- lights = curr.sub.-- lights & 0xAC;                         break;                                                                         }                                                                              break;                                                                         case RNWY.sub.-- 24 : case RNWY.sub.-- 06 :                                    switch (activity.sub.-- type)                                                  {                                                                              case NO.sub.-- ACTIVITY :                                                             curr.sub.-- lights = curr.sub.-- lights & 0x53;                         break;                                                                         }                                                                              break;                                                                         case RNWY.sub.-- INT :                                                         switch (activity.sub.-- type)                                                  {                                                                              case NO.sub.-- ACTIVITY :                                                      curr.sub.-- lights = 0;                                                        break;                                                                         }                                                                              break;                                                                         }                                                                              /* write new light settings to board */                                        outp(LIGHT.sub.-- ADDR,curr.sub.-- lights);                                    }                                                                              /*------------------------------------------------------------                 UNIT: update.sub.-- clearance.sub.-- lights                                    ______________________________________                                    

DESCRIPTION: this routine updates the specified clearance lights for a landing or takeoff operation. The landing/takeoff light for the specified runway is enabled, then the remaining landing/taxi lights for both runway ends are disabled.

    ______________________________________                                         INPUTS:                                                                               curr.sub.-- clear - clearance issued by ATC                             */                                                                             update.sub.-- clearance.sub.-- lights(short curr.sub.-- clear)                 /* based on current clearance, affected runway and the current                 status of the runway's lights, update the lights */                            switch (curr.sub.-- clear)                                                     {                                                                              case LANDING.sub.-- 35 :                                                       if ((curr.sub.-- lights & LANDING.sub.-- 35) == 0)                             curr.sub.-- lights = curr.sub.-- lights + LANDING.sub.-- 35;                   break;                                                                         case LANDING.sub.-- 17 :                                                       if ((curr.sub.-- lights & LANDING.sub.-- 17) == 0)                             curr.sub.-- lights = curr.sub.-- lights + LANDING.sub.-- 17;                   break;                                                                         case LANDING.sub.-- 24 :                                                       if ((curr.sub.-- lights & LANDING.sub.-- 24) == 0)                             curr.sub.-- lights = curr.sub.-- lights + LANDING.sub.-- 24;                   break;                                                                         case LANDING.sub.-- 06 :                                                       if ((curr.sub.-- lights & LANDING.sub.-- 06) == 0)                             curr.sub.-- lights = curr.sub.-- lights + LANDING.sub.-- 06;                   break;                                                                         case TAKEOFF.sub.-- 35 :                                                       if ((curr.sub.-- lights & TAKEOFF.sub.-- 35) == 0)                             curr.sub.-- lights = curr.sub.-- lights + TAKEOFF.sub.-- 35;                   break;                                                                         case TAKEOFF.sub.-- 17 :                                                       if ((curr.sub.-- lights & TAKEOFF.sub.-- 17) == 0)                             curr.sub.-- lights = curr.sub.-- lights + TAKEOFF.sub.-- 17;                   break;                                                                         case TAKEOFF.sub.-- 24 :                                                       if ((curr.sub.-- lights & TAKEOFF.sub.-- 24) == 0)                             curr.sub.-- lights = curr.sub.-- lights + TAKEOFF.sub.-- 24;                   break;                                                                         case TAKEOFF.sub.-- 06 :                                                       if ((curr.sub.-- lights & TAKEOFF.sub.-- 06) == 0)                             curr.sub.-- lights = curr.sub.-- lights + TAKEOFF.sub.-- 06;                   break;                                                                         }                                                                              /* write new light settings to board */                                        outp(LIGHT.sub.-- ADDR,curr.sub.-- lights);                                    }                                                                              /*------------------------------------------------------------                 UNIT: get.sub.-- runway.sub.-- clear                                           DESCRIPTION: determines the landing or takeoff flag setting                    INPUTS: int rw.sub.-- id - id of runway                                        char * msg.sub.-- type - arrival or takeoff                                    */                                                                             int get.sub.-- runway.sub.-- clear(int rw.sub.-- id, char *msg.sub.--          type)                                                                          {                                                                              /**- local variables -**/                                                      int clear.sub.-- stat; /* clearance status */                                  /* update current clearance (clear.sub.-- stat) based on the designated        runway (rw.sub.-- id) and type of clearance (ARRIVAL) or (TAKEOFF) */          switch (rw.sub.-- id)                                                          {                                                                              case RNWY.sub.-- 35 :                                                          if(strstr(msg.sub.-- type,"ARR") != NULL)                                      clear.sub.-- stat = LANDING.sub.-- 35;                                         else                                                                           clear.sub.-- stat = TAKEOFF.sub.-- 35;                                         break;                                                                         case RNWY.sub.-- 17 :                                                          if (strstr(msg.sub.-- type,"ARR") != NULL)                                     clear.sub.-- stat = LANDING.sub.-- 17;                                         else                                                                           clear.sub.-- stat = TAKEOFF.sub.-- 17;                                         break;                                                                         case RNWY.sub.-- 24 :                                                          if (strstr(msg.sub.-- type,"ARR") != NULL)                                     clear.sub.-- stat = LANDING.sub.-- 24;                                         else                                                                           clear.sub.-- stat = TAKEOFF.sub.-- 24;                                         break;                                                                         case RNWY.sub.-- 06 :                                                          if (strstr(msg.sub.-- type,"ARR") != NULL)                                     clear.sub.-- stat = LANDING.sub.-- 06;                                         else                                                                           clear.sub.-- stat = TAKEOFF.sub.-- 06;                                         break;                                                                         default :                                                                      clear.sub.-- stat = SURFACE;                                                   }                                                                              return(clear.sub.-- stat);                                                     }                                                                              /*------------------------------------------------------------                 UNIT: process.sub.-- clearance                                                 ______________________________________                                    

DESCRIPTION: process₋₋ clearance parses the clearance or departure message issued by the controller via the touch screen. update₋₋ clearance₋₋ lights is then called to change the specified light settings.

    ______________________________________                                         The message format is : $ATC,002,veh id,waypoint id                            for arrival (landing) waypoints and                                                     $ATC,004,veh id,waypoint id                                           for departure (takeoff) waypoints                                              INPUTS:                                                                               char clearance.sub.-- msg[MAX.sub.-- STR]                               */                                                                             process.sub.-- clearance(char clearance.sub.-- msg[MAX.sub.-- STR])            /**- local variables -**/                                                      char wp.sub.-- id[12]; /* waypoint id   */                                     char *token; /* character field from ATC msg  */                               int rw.sub.-- id; /* id of runway cleared for operation */                     int veh.sub.-- index; /* index into veh database for current veh */            int slen; /* string length   */                                                int i; /* counter   */                                                         /* parse clearance message */                                                  token = strtok(clearance.sub.-- msg,","); /* $ATC */                           token = strtok(NULL,",");  /* message type */                                  token = strtok(NULL,",");  /* vehicle id */                                    strcpy(veh.sub.-- cleared,token);                                              token = strtok(NULL,",");  /* waypoint id */                                   /* extract waypoint information */                                             slen = strlen(token) -2;                                                       for (i = 0; i < slen; i++)                                                     wp.sub.-- id[i] = token[i];                                                    wp.sub.-- id[i] = `\0`;                                              /* get runway id from waypoint information */                                  if (strstr(wp.sub.-- id,"35") != NULL)                                         rw.sub.-- id = RNWY.sub.-- 35;                                                 else                                                                           if (strstr(wp.sub.-- id,"24") != NULL)                                         rw.sub.-- id = RNWY.sub.-- 24;                                                 else                                                                           if (strstr(wp.sub.-- id,"17") != NULL)                                         rw.sub.-- id = RNWY.sub.-- 17;                                                 else                                                                           if (strstr(wp.sub.-- id,"06") != NULL)                                         rw.sub.-- id = RNWY.sub.-- 06;                                                 else                                                                           rw.sub.-- id = 0;                                                              /* find vehicle in vehicle database */                                         veh.sub.-- index = find.sub.-- veh.sub.-- index(veh.sub.-- cleared);           if (veh.sub.-- index != -1) /* if vehicle found in database */                 {                                                                              /* set clearance based on message type and selected runway */                  current.sub.-- clearance = current.sub.-- clearance -                                  veh[veh.sub.-- index].clear.sub.-- status;                             veh[veh.sub.-- index].clear.sub.-- status = get.sub.-- runway.sub.--           clear(rw.sub.-- id,wp.sub.-- id);                                              current.sub.-- clearance = veh[veh.sub.-- index].clear.sub.-- status +                 current.sub.-- clearance;                                              /* extract and store waypoint data */                                          store.sub.-- wps(wp.sub.-- id,veh[veh.sub.-- index].wpindex);                  veh[veh.sub.-- index].currwp = NO.sub.-- WP;                                   end.sub.-- of.sub.-- wps = FALSE;                                              /* update lights immediately for arrival aircraft */                           if (strstr(wp.sub.-- id,"ARR") != NULL)                                        update.sub.-- clearance.sub.-- lights(current.sub.-- clearance);               }     /* if vehicle in database */                                             }                                                                              ______________________________________                                    

CLEARANCE DELIVERY

If the vehicle is entering or inside a runway zone and the vehicle has a clearance, a runway incursion is not detected. A clearance is issued by the AC&M operator using the ARRIVAL WAYPOINTS, DEPARTURE WAYPOINTS or SURFACE WAYPOINTS functions.

When a clearance is issued, a global CURRENT₋₋ CLEARANCE flag is updated. The CURRENT₋₋ CLEARANCE flag is used to maintain the current airport light settings. A separate clearance status flag is also maintained in the vehicle database for each vehicle. As the vehicle approaches a runway zone, its clearance status flag is read to determine whether a runway incursion condition should be generated. Clearances are terminated automatically when the vehicle reaches the last waypoint. Clearances may also be manually cleared by the AC&M operator through the CLEAR PATH WAYPOINTS function. When the clearances are terminated, the global CURRENT₋₋ CLEARANCE flag and individual vehicle clearance flags are updated.

ECEF WAYPOINT NAVIGATION

After waypoints have been issued to a vehicle or vehicles, the AC&M performs a set of navigation functions, mirroring those performed on board the vehicle using the ADS position reports. A set of waypoints is maintained for each cleared vehicle. The vehicle's current 3-D range to the waypoint and cross track error is computed for each subsequent ADS report. A determination as to whether the vehicle is on or off course is also made. If an off course condition is detected, a warning message is displayed to the operator in the AC&M's Alerts window.

To support the AC&M's mirrored navigation processing, the following fields are maintained in the vehicle database:

Waypoint index

Current Waypoint

Cross Track Error

3D Range to Waypoint

Wrong Way Indicator

The Waypoint Index is the ID of the waypoint list assigned to the vehicle and the Current Waypoint is the waypoint the pilot is navigating towards.

At any time after the assignment of waypoints to the vehicle, the vehicle's 3-D range to the waypoint, cross track error, current waypoint, speed and heading information may be displayed in the MC&R window using the VEHICLE DATA function.

GRAPHICS PROCESSOR AND AC&M INTERFACE

The Graphics Processor (GP) 122 interfaces to the AC&M Processor 121 via a dedicated communication link 123. The GP is currently based on a 66 mHz 486 processor with a VESA Video Local Bus. The processor performs the following functions:

Receives graphics commands from AC&M

Interprets graphics commands

Performs the graphic display functions

Provides situational awareness capability

Manages the view and content of the display presentation

Maintains local map-based waypoint, zone and map layer databases

Interface with large graphics display hardware

Two types of messages are received by the GP:

(1) vehicle position messages

(2) display commands

Upon receipt of an ADS report, the AC&M Processor converts the vehicle's ECEF X,Y,Z position to the map's coordinate system if required and determines the appropriate map layer for the vehicle based on the vehicle's type and any collision or zone incursion conditions. If the vehicle is moving, the newly formatted message is sent to the GP. Stationary vehicle's are not redisplayed in the map but remain displayed in their last reported position. The message format is shown below:

$TRK,vehicle id,map layer,map x,map y,mapz coordinates<CR><LF>

Display commands are also generated by the AC&M Processor 121 and sent to the GP 122. Numerous AC&M commands, including ARRIVAL WAYPOINTS, DEPARTURE WAYPOINTS, SURFACE WAYPOINTS, CLEAR PATH WAYPOINTS, DISPLAY VIEW, VEHICLE FILTER and LAYER FILTER affect the display presentation on the GP. An acknowledgement is returned to the AC&M Processor 121 when a display command message is received by the GP 122.

LAYER ASSIGNMENTS

The GP 122 supports up to 256 unique layers which are used for the display and segregation of graphic information. The layer assignments are provided below.

    ______________________________________                                         MAP LAYER ASSIGNMENTS                                                          LAYER #                                                                               DESCRIPTION            MODE                                             ______________________________________                                         0-2    AIRPORT MAP RUNWAYS, TAXIWAYS,                                                                        ALWAYS                                                  TRAVEL PATHS                                                            3      RANGE RINGS            ON DEMAND                                        4      EXPANSION              TBD                                              5      RANGE RINGS, 5 MILE INCREMENTS                                                                        ON DEMAND                                        6-8    EXPANSION              TBD                                              9      AIRPORT LIGHTING SYSTEMS                                                                              ON DEMAND                                               (RNWY 35)                                                               10     AIRPORT LIGHTING SYSTEMS                                                                              ON DEMAND                                               (RNWY 24)                                                               11     TRACKED SURFACE VEHICLES                                                                              ALWAYS                                                  (LIMITED ACCESS)                                                        12     TRACKED SURFACE VEHICLES                                                                              ALWAYS                                                  (FULL ACCESS)                                                           13     TRACKED DEPARTURE AIRCRAFT                                                                            ALWAYS                                           14     TRACKED ARRIVAL AIRCRAFT                                                                              ALWAYS                                           15-19  EXPANSION              TBD                                              20     ARRIVAL WAYPOINTS      ON DEMAND                                        21     DEPARTURE WAYPOINTS    ON DEMAND                                        22     SURFACE WAYPOINTS      ON DEMAND                                        23     CUSTOM WAYPOINTS DEFINITION                                                                           ON DEMAND                                        24     EXPANSION              TBD                                              25     AIRPORT SURFACE ZONES  ON DEMAND                                        26     WEIGHT LIMITED ZONES   ON DEMAND                                        27     RESTRICTED TRAVEL AREA ON DEMAND                                               (WINGSPAN, ETC.)                                                        28     AIRSPACE HAZARD ZONES  ON DEMAND                                        29     OPEN CONSTRUCTION ZONES                                                                               ON DEMAND                                        30     CLOSED CONSTRUCTIONS ZONES                                                                            ON DEMAND                                        31-60  EXPANSION              TBD                                              61     WATCH LAYER (COLOR = YELLOW)                                                                          ALWAYS                                           62     WARNING LAYER (COLOR = RED)                                                                           ALWAYS                                           ______________________________________                                    

VEHICLES AC&M SYSTEM FUNCTIONAL MATRIX

Many of the functions performed at the AC&M Processor are also performed on board the vehicles. These vehicles, equipped with varying configurations of hardware and software, have been used in a number of prototype demonstrations. The matrix below lists the major functions and the vehicles on which they are performed.

    __________________________________________________________________________     VEHICLE FUNCTIONAL MATRIX                                                                               FULL   LIMITED                                                                 ACCESS ACCESS                                         FUNCTION     AC&M AIRCRAFT                                                                              VEHICLE 1                                                                             VEHICLE 2                                      __________________________________________________________________________     Receive & process DGPS                                                                      N    Y      Y      Y                                              corrections                                                                    Formats and transmits                                                                       N    Y      Y      Y                                              ADS posn & vel. data                                                           Receives remote ADS                                                                         Y    N      Y      N                                              messages                                                                       Displays ADS positions                                                                      Y    N      Y      N                                              in map display                                                                 Performs dynamic                                                                            Y    N      Y      N                                              collision processing                                                           Performs zone incursion                                                                     Y    Y      Y      Y                                              processing                                                                     Performs runway incursion                                                                   Y    N      N      N                                              processing                                                                     Controls airport lights                                                                     Y    N      N      N                                              Formats ATC commands                                                                        Y    N      N      N                                              Receives ATC commands                                                                       N    Y      Y      Y                                              Performs waypoint                                                                           Y    Y      Y      N                                              navigation                                                                     Displays current position                                                                   N    Y      Y      N                                              in moving map display                                                          __________________________________________________________________________

Hardware block diagrams for each of the three prototype vehicle types are provided in the figures which follow, starting with the Aircraft System FIG. 24.

Differential GPS data is provided by a GPS GOLD DGPS receiver 124 and a differential data link 125. GPS position, velocity, and time information is supplied to the dual 486 based processing unit. The first 486 processor, or Navigation (NAV) Processor 126, receives GPS Receiver 124 information and performs the following functions:

Coordinate conversions from Lat/Lon/MSL to ECEF X, Y, Z

Position projections

Zone and runway incursion checking

Map layer control

General ECEF waypoint navigation and on/off course processing

ECEF-based precision landing navigation

Access to waypoint and zone databases

Transmission of graphic instructions to second 486 processor 127

Broadcast of position and velocity data over ADS datalink 128

Control of communication digital datalinks

Support for monochrome flat panel display 129

The second 486 processor, the Aircraft Graphics Processor (AGP) 127, receives graphics instructions from the NAV Processor 126 and performs the following functions:

Graphics command translations and interpretations

Graphic display functions

Display presentation view and content management

Support for monochrome flat panel display 130

The functions supported in the aircraft are actually a slightly modified version of those performed by the AC&M Subsystem. The use of common hardware and operational software elements simplified the prototype demonstration development efforts.

The full access surface vehicle (Vehicle #1) high level block diagram is provided in FIG. 25.

Again, differential GPS data is provided by a DGPS receiver 131 and a differential data link 132. GPS position, velocity, and time information are supplied to the dual 486 based processing unit. The first 486 processor, the Navigation Processor (NAV) 133, receives GPS information and performs the following functions:

Coordinate conversions from Lat/Lon/MSL to ECEF X, Y, Z

Position projections

Collision prediction processing

Zone and runway incursion checking

Layer control

General ECEF waypoint navigation (optional)

Access to vehicle, waypoint and zone databases

Transmission of graphic instructions to second 486 processor 134

Broadcast of position and velocity data over ADS datalink 135

Receipt of remote ADS messages from other vehicles

Control of communication digital datalinks

Support for flat panel LCD display

The second 486 processor, the Vehicle Graphics Processor (VGP) 134 receives graphics instructions from the NAV Processor 133 and performs the following functions:

Graphics command translations and interpretations

Graphic display functions

Situational awareness capability

Display presentation view and content management

Support for flat panel LCD display 136

The functions supported in the full access surface vehicle are identical to those performed in the aircraft with a couple of additions. The full access vehicle receives remote ADS messages from other vehicles operating within the airport space envelope. This information is used to provide a situational awareness capability on board the vehicle. Full collision detection processing is also implemented.

The limited access surface vehicle (Vehicle #2) is equipped with developed hardware and software as shown in FIG. 26.

Since no graphic display is provided on Vehicle #2, a single 386-based processor 137 is utilized. Again, differential GPS data is provided by an on board DGPS receiver 138 and a differential data link 139. GPS position, velocity, and time information is supplied to the 386 based processing unit 137 which performs the following functions:

Coordinate conversions from Lat/Lon/MSL to ECEF X, Y, Z

Position projections

Zone and runway incursion checking

Access to zone database

Sounds audible warning when zone incursion is detected 140

Broadcast of position and velocity data over ADS datalink 141

The functions supported in Vehicle #2 are actually a subset of those supported in the aircraft and Vehicle #1.

COMMUNICATIONS

Each vehicle is equipped with a VHF/UHF radio capable of full duplex communications. The radio interfaces to an integrated modem/GPS interface card. The radio modem is used to receive differential corrections, ADS messages, and ATC command messages forwarded by the COMM Processor. Local GPS messages are received by the vehicle's Navigation (NAV) processor. The GPS position and velocity data is converted to the ECEF coordinate frame, reformatted and transmitted to the AC&M Processor over the same radio.

NAVIGATION PROCESSOR AND NAVIGATION

Navigation functions are performed on board the vehicle when waypoints are received from the AC&M Processor via the VHF datalink. Two navigation screens are provided, a cross hairs display for airborne applications and a map-based display for ground operations.

Upon receipt of the waypoint message from the AC&M Processor, the waypoint id is extracted and used to identify the predefined waypoint path. The waypoints are automatically loaded into the vehicle's ECEF navigation system and drawn into the vehicle's map display. FIG. 27 shows the airborne navigation display produced with the previously listed software routines.

The navigation display format is unique since it provides conventional course, bearing and range information and actual position with respect to the true course. The display portion on the right side of the screen is driven by NEU surface parameters while the display at the left is driven directly by ECEF X, Y, Z parameters. This display format may be used for all phases of flight.

The algorithms for 3-D range to the waypoint, transitioning to the next waypoint, cross track error, on/off course and wrong way determination are identical to those performed at the AC&M Processor.

For ground taxi operators, map-based waypoint navigation was found to be preferable. FIG. 8 shows a waypoint path from the Crash, Fire and Rescue (CFR) Station to the East Terminal Ramp drawn in the on board digital map display.

FIG. 9 depicts the predefined waypoint path for a departure on Runway 35.

ZONES PROCESSING

All surface vehicles are capable of performing static zone incursion processing. The zone processing algorithms are identical to those implemented at the AC&M system with the addition of an audible tone generated when an incursion occurs.

COLLISION DETECTION PROCESSING

This fully equipped vehicle (FEV) is capable of performing collision prediction processing based on the vehicle's current position (and velocity) and the remote vehicles' ADS messages.

As the ADS messages are received, they are parsed and stored in the local vehicle database. Collision processing is performed each second, upon receipt of the FEV's GPS position and velocity data. After each GPS update, projections are performed on the FEV's current position and compared to the projected positions for each vehicle stored in the local database. In the same manner as described for the AC&M Processor, potential collision watch and warning conditions are detected between the FEV and other vehicles. However, collisions between two remote vehicles are not detected. Collisions tests are only performed with respect to the FEV itself and those in its vicinity.

GRAPHIC PROCESSOR AND MOVING MAP DISPLAY

Both the FEV and the aircraft are capable of displaying their current position with respect to an on board moving map display. As the vehicle's position approaches the edge of the map display, the map is automatically panned and redrawn with the vehicle centered in the display. When the vehicle is on the airport surface, the map is drawn with a north orientation at a 0.25 mile plan view perspective. When the vehicle is more than one mile from the center of the map, the map is automatically redrawn at a ten (10) mile scale.

SITUATIONAL AWARENESS

The FEV is capable of displaying the positions of remote vehicle positions in the on board moving map display. As ADS messages are received from the COMM processor, the remote vehicles' positions are checked to see if they would appear on the current display view. If the positions are outside of the current view, they are discarded. Positions within the current view are drawn into the map display.

LAYER--COLOR CONTROL

As at the AC&M processor, the FEV's situational awareness display uses color cues to indicate vehicles in a collision or zone incursion condition. As ADS and GPS messages are received and processed by the on board NAV Processor, graphics messages are formatted and sent to the local Graphics Processor (GP). These graphics messages are identical to those created at the AC&M Processor and include the vehicle id, layer id and map x,y,z position. ##SPC4##

OVER COMING ERROR SOURCES MAP TEMPORAL DIFFERENTIAL CORRECTION

Map temporal differential corrections are a simple and effective means of reducing error sources in GPS operation for short periods of time when Selective Availability is not active. FIG. 31 depicts the map temporal correction elements.

Map temporal corrections utilize at least one precisely surveyed location in the local area. The surveyed location may be determined from a monument marker or may be determined using a highly accurate digital or paper map. A GPS receiver and (optionally) a processing computer are co-located at the known location with the GPS antenna carefully positioned at the survey point. The receiver/computer remains at the known location for a period of time and, when enough data has been collected, determines pseudo range correction and pseudo range rate factors. These correction factors may then be applied to the differential GPS receiver to determine a corrected position. These factors are used in subsequent position determinations until another map temporal correction is applied.

Map temporal corrections are the simplest form of closed loop differential correction. As the name implies, temporal corrections degrade with time as the receiver moves within the local area. SA significantly reduces the benefits of a temporal differential correction approach. When SA is not active, the short term (30 minute) accuracy of this technique is very good (a meter or two), since all error sources are reduced. One additional limiting factor is that the same satellites must be used during roving operations as those used at the surveyed location. This may be accomplished through software control to ensure a `selected` set of satellites are used for a given GPS session.

REGIONAL DIFFERENTIAL CORRECTIONS AND DIFFERENTIAL OVERVIEW

Real time differential correction techniques compensate for a number of error sources inherent to GPS. The idea is simple in concept and basically incorporates two or more GPS receivers, one acting as a stationary base station and the other(s) acting as roving receiver(s). The differential base station is "anchored" at a known point on the earth'surface. The base station receives the satellite signals, determines the errors in the signals and then calculates corrections to remove the errors. The corrections are then broadcast to the roving receivers.

Real time differential processing provides accuracies of 10.0 meters or better (typically 1.0-5.0 meters for local differential corrections). The corrections broadcast by the base station are accurate over an area of about 1500 km or more. Typical positional degradation is approximately a few millimeters of position error per kilometer of base station and roving receiver separation. FIG. 32 shows the basic elements for real time differential GPS (DGPS) operations.

Through the implementation of local differential GPS techniques, SA errors are reduced significantly while the atmospheric errors are almost completely removed. Ephemeris and clock errors are virtually removed as well.

    ______________________________________                                         ERROR SOURCES CORRECTED OR REDUCED DY DGPS                                     USER RANGE ERRORS (URE)                                                        1 SIGMA MAGNITUDES                                                                            WITHOUT DGPS                                                                              WITH DGPS                                            ______________________________________                                         SATELLITE CLOCK & NAV.                                                                          2.7          0                                                EPHEMERIDES & PREDICTION                                                                        2.7          0                                                ATMOSPHERIC      9.0          0                                                IONOSPHERIC                                                                    TROPOSPHERIC     2.0          .15*                                             SELECTIVE AVAILABILITY                                                                          30.0#        0                                                TOTAL RSS        31.6         .15                                              ______________________________________                                          * Tropospheric effects are a local phenomenon and are a function of the        altitude difference from the base station to the roving receiver and the       local elevation angle of the satellite.                                        # To counteract the effects of SA, differential corrections must be            generated, transmitted and utilized in the GPS receiver at a rate              sufficient to compensate for the rate of change of SA.                   

Differential GPS can introduce an additional error, if not employed properly. The age of the differential correction must be monitored at the GPS receiver. As the differential correction ages, the error in the propagated value increases as well. This is particularly true for `virulent` strains of SA where the errors introduced slew quickly over very short time intervals.

OPERATIONAL ELEMENTS

The precisely surveyed location of the GPS antenna is programmed into the reference station as part of its initial installation and set up procedures. Industry standard reference stations determine pseudo range and delta range based on carrier smoothed measurements for all satellites in view. Since the exact ECEF position of the antenna is known, corrections may be generated for the pseudo range and delta range measurements and precise time can be calculated.

Naturally occurring errors are, for the most part, slow changing and monotonic over the typical periods of concerns. When SA is not invoked, delta range corrections provide a valid method of improving positional accuracy at the roving receivers using less frequent correction broadcasts. With the advent of SA and its random, quick changing non-monotonic characteristics, delta range corrections become somewhat meaningless and may actually degrade the system performance under some conditions.

As shown previously in FIG. 32, the DGPS correction messages are broadcast by the reference station and received by the roving receivers. The corrections are applied directly to the differential GPS receiver. The DGPS receiver calculates the pseudo range and the delta range measurements for each satellite in the usual manner. Prior to performing the navigation solution, the received pseudo range and delta range corrections are applied to the internal measurements. The receiver then calculates corrected position, velocity and time date. Typical DGPS position and velocity performance is presented in the table below.

    ______________________________________                                         COMPARISON OF TYPICAL GPS POSITION AND VELOCITY                                MEASUREMENTS USING COMMERCIAL NAVIGATION TYPE                                  RECEIVERS (ACCURACIES ARE A FUNCTION OF CORRECTION                             AGE) THIS EXAMPLE USES CORRECTION AGE = 5 SECONDS                                       WITHOUT DGPS WITH DGPS                                                         CODE   CARRIER   CODE     CARRIER                                              RCVR   RCVR      RCVR     RCVR                                        ______________________________________                                         2-D POSITION                                                                              <100 M   <40 M     <10 M  <2 M                                      3-D POSITION                                                                              <176 M   <80 M     <18 M  <4 M                                      VELOCITY knots                                                                            <10 KN   <5 KN     <.1 KN <.1 KN                                    TIME*      <300 ns  <100 ns   <100 ns                                                                               <50 ns                                    ______________________________________                                          *The time accuracy is highly dependent upon the type of receiver.              Specialized, precise time receivers provide accuracies in the 5 to 25          nanosecond range. Most navigational receivers do not provide this level o      time accuracy since it is not required for general navigation.           

Since differential GPS eliminates most GPS errors, it provides significant improvements in system reliability for life critical airport operations. Short term and long term drift of the satellite orbits, clocks and naturally occurring phenomenon are compensated for by differential GPS as are other potential GPS satellite failures. Differential GPS is mandatory in the airport environment from a reliability, accuracy and fault compensating perspective.

As with autonomous GPS receiver operation, multipath is a potential problem. The differential reference station cannot correct for multipath errors at the roving receiver(s). Antenna design and placement considerations, and receiver design characteristics remain the best solutions to date in the minimization of multipath effects.

DGPS provides the means to eliminate most GPS system errors. The remaining errors are related to receiver design and multipath. Not all GPS receivers and reference stations are created equal, some are distinctly better than others. The selection of the reference station and the roving receivers has a significant effect on the overall system accuracy.

COMPENSATING FOR RECEIVER ERROR

Receiver errors are not corrected using an `open loop` differential correction method as described above. These errors may be reduced when a `closed loop` differential technique is employed. FIG. 33 presents a high level block diagram of a `closed loop` differential system.

FIG. 33 has additional elements over the standard differential system configuration. A second GPS antenna is installed at a precisely surveyed antenna location and a stationary GPS receiver is co-located with the reference station. This receiver accepts differential correction inputs generated by the reference station. The stationary GPS receiver incorporates the pseudo range corrections in the normal manner and determines DGPS position and velocity. The corrected position and velocity are then compared to the stationary receivers known position and velocity (0,0,0). The ECEF delta position and velocity data are then used by the reference station processing to further refine the pseudo range and delta range corrections which are broadcast to the roving receivers. Processing software which minimizes the position and velocity errors is used. This technique requires that the roving receivers be identical to the stationary GPS receiver located at the reference station site. That is, the roving receivers must exhibit receiver errors similar to those on the stationary DGPS receiver.

INTEGRITY AND MULTI-SENSOR SYSTEMS

The issues of integrity and fault monitoring are a major concerns for any technology considered for the life critical application of air transport and air traffic control. The integration of GPS with other technologies provides a higher degree of fault detection capability, a potentially improved GPS navigational performance, and the potential of limited navigation support should a catastrophic GPS failure occur aboard the vehicle.

The integration of GPS with an inertial system can be used to improve the dynamic performance of the navigation solution. Dynamic sensors may provide jerk, acceleration and velocity information to aid in the navigation solution. Sole means inertial navigation may be used in conjunction with GPS. The integration of GPS with inertial systems usually require 12 (or higher) state Kalman filter solutions techniques.

The concept of Receiver Autonomous Integrity Monitoring (RAIM) is accepted as a potential integrity monitoring system. The RAIM concept requires that the GPS receiver and/or navigation system include the required "smarts" to diagnose its own health using additional satellites, redundant hardware and specialized internal software processing. RAIM standards are currently being developed for industry approval.

When combined with other sensors such as WAAS, inertial, baro altimeter and internal RAIM processing, GPS will have superior accuracy, fault tolerance and fault detection capability.

FAULT TOLERANCE AND HIGH AVAILABILITY

Any system which controls life critical operations at an airport must support fault tolerance and high availability. At the same time, the system must be cost effective and support technology insertion. High system availability may be achieved through a custom design process utilizing selected and screened components for high Mean Time Between Failure (MTBF). Alternatively, high availability may be achieved through system redundancy using components of non-custom, commercial-off-the-shelf design. The following paragraphs introduce a few of the concepts which are later utilized in the system₋₋ design analysis.

AVAILABILITY: Availability is defined as the probability that a system will operate to specification at any point in time, when supported with a specific level of maintenance and spares.

MEAN TIME BETWEEN FAILURES (MTBF): The mean time a piece of equipment will remain operational before it is expected to fail.

RELIABILITY: The inherent probability that a piece of equipment or hardware will remain operational for a period of time (t). It is expressed as follows: ##EQU1##

TRAVEL TIME: The travel time is measured from the time of failure to the time the repair technician and required spare parts arrive at the failed equipment.

MEAN TIME TO RECONFIGURE (MTTC): The mean time a system is inoperable as measured from the time of failure to the time of full operation. Typically, reconfiguration time involves bringing on line redundant systems in an effort to provide continued service.

MEAN TIME TO REPAIR AND CERTIFY (MTTRC): The mean time of the actual repair and recertification activities as measured from the time of arrival to the failed equipment to the time which the equipment is on line, certified and declared operational.

MEAN TIME TO REPAIR (MTTR): MTTR is the sum of TRAVEL+MTTC+MTTRC. AVAILABILITY EXAMPLE

The following analysis builds upon elements of the system composed of off the shelf components arranged in a redundant configuration. Commercial industrial single board computers are connected with other commercial elements of the manner as shown in the FIGS. 28, 29, 30. This approach provides cost effectiveness. COTS technology insertion, declining COTS life cycle costs and high availability. The analysis starts with no design redundancy FIG. 28, and ends describing a two controller station redundant architecture FIG. 30.

This example will determine the overall reliability and availability of the architecture shown in FIG. 28. The requirement for system availability for this terminal area system comes from the FAA Advanced Automation Program (AAS). The AAS program defines the system yearly availability to be 0.99995 determined using a 2 hour travel time which is added to any other system down time. The major elements of the airport system shown in FIG. 28.

    __________________________________________________________________________     KEY OPERATIONAL PARAMETERS                                                     AVAILABILITY *        AVAIL := 0.99995                                         TRAVEL TIME (HRS) *   TRAVEL := 2.0                                            * = FROM FAA ADVANCED AUTOMATION SPECIFICATION                                 TIME TO AUTO CONFIGURE (HRS)                                                                         MTTC := .025 90 SECONDS                                  MEAN TIME TO REPAIR AND CERTIFY (HRS)                                                                MTTRC := .25                                             (TESTED SPARES, FAULT ISOLATED TO LRU)                                         MEAN TIME TO REPAIR (MTTR)  MTTR := MTTRC + MTTC + TRAVEL  MTTR = 2.275        SPECIFIC COMPONENT PARAMETERS                                                  SINGLE BOARD COMPUTER 142, 143 MEAN TIME BETWEEN FAILURES (HRS)                SBC := 90000                                                                   SBC RELIABILITY (RSBC)                                                          ##STR61##               RSBC = 0.907254                                       DIGITAL RADIO TRANSCEIVER 144 MEAN TIME BETWEEN FAILURES (HRS)                 XCVR := 75000                                                                  DIGITAL RADIO TRANSCEIVER RELIABILITY (RXMTR)                                   ##STR62##               RXCVR = 0.889763                                      TOUCH SCREEN 145 MEAN TIME BETWEEN FAILURES (HRS) TOUCH := 100000              TOUCH SCREEN RELIABILTY (RTOUCH)                                                ##STR63##               RTOUCH = 0.916127                                     LOW VOLTAGE DC POWER SUPPLY 146 MEAN TIME BETWEEN FAILURES (HRS)               LVPS := 500000                                                                 LOW VOLTAGE POWER SUPPLY RELIABILITY (RLVPS)                                    ##STR64##               RLVPS = 0.982633                                      FLAT SCREEN DISPLAY 147 MEAN TIME BETWEEN FAILURES (HRS) DIS := 75000          FLAT SCREEN DISPLAY RELIABILITY (RDIS)                                          ##STR65##               RDIS = 0.889763                                       AIRPORT LIGHTING UNIT 148 MEAN TIME BETWEEN FAILURES (HRS)                     Interface only, no light bulbs or individual light switches                    LITE = 250000                                                                  AIRPORT LIGHTING UNIT RELIABILITY (RLITE)                                       ##STR66##               RLITE = 0.965567                                      REDUNDANT ARRAY of INEXPENSIVE DISKS (RAID 149 MTBF (HRS)                      RAID := 150000                                                                 RAID RELIABILITY (RRAID)                                                        ##STR67##               RRAID = 0.943273                                      LOCAL AREA NETWORK 150 MEAN TIME BETWEEN FAILURES (HRS)                        LAN = 87600                                                                    LOCAL AREA NETWORK RELIABILITY (RLAN)                                           ##STR68##               RLAN = 0.904837                                       KEYBOARD 151 MEAN TIME BETWEEN FAILURE (HRS)                                   KBD = 75000                                                                    KEYBOARD RELIABILITY (RKBD)                                                     ##STR69##               RKBD = 0.889763                                       DIFFERENTIAL BASE STATION 152 MEAN TIME BETWEEN FAILURES (HRS)                 DIFF := 100000                                                                 DIFFERENTIAL BASE STATION RELIABILITY (RDIFF)                                   ##STR70##               RDIFF = 0.916127                                      __________________________________________________________________________

This particular analysis is for a single controller station, multiple stations could be used simply by duplicating the design elements. The controller must have the following capabilities to perform his airport duties:

1. have full duplex voice and data communications

2. a controlling AC&M display and graphic display

3. a command touch screen capability or keyboard

4. differential GPS for all navigation

5. airport lighting interface (independent bulbs and switches may fail without loss of function)

The minimal set of controller actions require the following hardware and associated software to be operational.

1. radio transceiver (voice and data function)

2. AC&M display, SBC server, and RAID

3. Graphic display, SBC,

4. a low voltage power supply

5. a command and control touch screen or a keyboard

6. minimal configuration operational software

7. a LAN assembly

8. a differential GPS base station

9. a airport lighting interface

The hardware elements can be connected in a minimal hardware configuration and the overall availability can be compared to the specified value of 0.99995 ##EQU2## The initial MTBF for the series string is determined below. ##EQU3## Initial availability based upon series minimum configuration is ##EQU4##

As expected availability does not meet the specification, system redundancy will be necessary to achieve the design goal. To meet the required availability a system MTBF of about 45,000 hours will be necessary with a 2.275 hour mean time to repair. A new architecture is shown in FIG. 29.

AIRPORT SYSTEM, SINGLE REDUNDANT CONTROLLER STATION

Redundant radio transceivers will be necessary since a single point failure is unacceptable in this component. Parallel radio transceiver reliability is determined below: ##EQU5## Redundant LVPS are required for the same reason ##EQU6## Redundant Local Area Networks are also required, since a single point failure can not be tolerated in communications between the AC&M SBC and Graphic SBC. ##EQU7## Redundant Differential GPS are also required, since a ₋₋ single point failure can not be tolerated in airport navigation functions. ##EQU8## Redundant airport lighting control interfaces are required ##EQU9## The keyboard and the touch screen provide the same capability, hence may be treated as a parallel redundant system element. The keyboard/touch screen combination is found below: ##EQU10## An extra display surface will be added to display information. This display capability will be used should a failure occur in an AC&M display or in a graphic situation display. A 2 of 3 display scenario is used for successful mission completion. Should a failure occur auto reconfiguration must occur within the specified time allocation. To determine exactly what the 2 our of 3 display process represents, a probability analysis is performed. The probability is determined from the series elements which make up the display function. One display channel may fail while the two others provide the necessary information. The third display is used to provide non mission critical information when acting as a hot spare.

SERIES DISPLAY CHANNEL ELEMENTS ##EQU11## In the 2 of 3 scenario the possible operating combinations must add to one; meaning the probability of all of the possible operating modes must add to 1. The operating combinations are identified below:

1. all 3 serial display channels are operational

2. one channel is down and the other two are operational

3. two channels are down and only one is operating

4. all channels are down ##EQU12##

From a hardware perspective the system meets requirements. The system software must be able to detect hard and soft failures and must be able to fault isolate the failed device. Parallel hardware redundancy and "smart" software provide the necessary fault monitoring, fault containment and fault identification to the LRU level. Operational software is tailored to the specific application, but the hardware is based upon. COTS standards to allow for failure technology insertion and cost effective replacement.

Multiple controller stations may be added to support larger airport systems. In this case a slightly different architecture is utilized. Common elements are shared by multiple stations. In the 2 station architecture shown parallel differential GPS base stations, parallel lighting control interfaces, parallel Local Area Networks and parallel transceivers are utilized. Since a redundant capability is provided with multiple controller stations consisting of 2 of 3 scenario increased availability is provided as shown in FIG. 30. ##EQU13##

Further availability improvements and cost reduction may be realized when configured with multiple controller stations. The 2 of 3 display channel operation may be reduced to 2 single display channels and RAIDS may be eliminated while still meeting availability goals when operating with multiple redundant reconfigurable controller stations.

AIRPORT LAYOUT PLAN

The U.S. FAA recommends the development of digitized Airport Layout Plans (ALPs). In an ALP, the existing and proposed land and facilities required in the operation and development of the airport are provided in a scaled drawing. Each ALP should include the following information:

airport facilities--runways, taxiways, ramps, service roads, navigation aids, and buildings

airspace matters--existing and planned approach/missed approach/departure procedures, special use and controlled airspace, control zones and traffic patterns

obstructions to air and ground navigation

airport topography

precise airport monumentation

If designed properly, the ALP should be suitable for use in airport master plan activities, emergency work, maintenance, navigation and ATC.

GPS COMPATIBLE MONUMENTATION

Airport ALP generation or mapping activities may use any number of map coordinate systems based on a number of earth datums or ellipsoid references. Standardization of the mapping techniques and references are key in the development of any successful multi-use mapping program. In addition to the selection of a standard reference system, the interface to the local area surrounding the airport must be addressed. Accurate cross referenced monumentation points are necessary to allow for a smooth transition between the local coordinate system and the one used in the airport maps or in the navigation system. In the U.S., local State Plane Coordinate Systems (SPCS) for the baseline for most local mapping activities. As such, the ALPs for all U.S. airports should be monumented with reference points to provide for accurate coordinate conversion between World Geodetic Survey of 1984 (WGS 84) Latitude--Longitude, Earth Centered Earth Fixed (ECEF) X, Y, Z and local SPCSs or Universal Transverse Mercator (UTM). GPS and conventional survey techniques are recommended for such monumentation.

The surveyed accuracy of the multi-use airport map is recommended to be better than 0.5 meters for the horizontal and 0.1 meter for elevation. Of particular interest are the Airport Runway Touch Down Marker Reference Points (the precise coordinates of the center of a runway's touch down marker) and the Airport Runway Reference Points (the precise coordinates along the centerline path of the runway). In addition, the precise locations of all turn outs and turn ins should be identified in the airport map database.

Earth reference systems used in these locations should be ECEF X,Y,Z, North American Datum of 1983 (NAD 83) or WGS 84 latitude, longitude, MSL. These three models are compatible with GPS-based navigation. Should the positions not be in one of these coordinate reference systems, then local airport multi-coordinate reference monumentation should be used to support the required coordinate conversions.

Airport map latitude, longitude projections should be based upon the Transverse Mercator, Lambert Conformal Conic, or Hotline Oblique Mercator. These projections are used in the state plane coordinate systems. Additional information on reference systems and projections is available in North American Datum of 1983 (NAD 83), by Charles R. Schwartz.

The Manchester, New Hampshire (NH) airport map used in numerous test activities was initially in NH State Plane Coordinate System feet. This coordinate system was chosen for compatibility with existing maps and because it represented distances in linear feet rather than in degrees of latitude and longitude. The map was later converted to NH state plane meters and ECEF X,Y,Z representations. Manchester Airport was carefully surveyed and monumentation was performed at multiple sites around the airport. The monumented points were referenced to the ECEF Cartesian Coordinate System, NAD 83 Latitude, Longitude and Mean Sea Level (MSL), and the NH State Plane. Coordinate conversions were performed using the monumented points shown below.

    ______________________________________                                         MULTI-REFERENCE MONUMENTATION                                                  FLAGPOLE          RUNWAY 35 END                                                MONUMENT SITE #1  MONUMENT SITE #2                                             ______________________________________                                         NEW HAMPSHIRE STATE PLANE COORDINATES                                          NH SPCS X = 1045137.57 FT E                                                                      NH SPCS X = 1048524.02 FT E                                  NH SPCS Y = 158006.05 FT N                                                                       NH SPCS Y = 154481.07 FT N                                   NH ALT = 225.04 FT                                                                               NH ALT = 215.73 FT                                           NH ALT = 68.59    M NH ALT = 65.75 M                                           NAD83 LAT,LON,MSL                                                              LAT83 = 42.933325800 N                                                                           LAT83 = 42.923628275 N                                       LON83 = 71.439298894 W                                                                           LON83 = 71.426691202 W                                       MSL = 225.04 FT   MSL = 215.73 FT                                              MSL ALT = 68.59 M MSL ALT = 65.75 M                                            ECEF X,Y,Z COORDINATES                                                         ECEF X = 1488741.9 M                                                                             ECEF X = 1489950.5 M                                         ECEF Y = -4433764.7 M                                                                            ECEF Y = -4434130.5 M                                        ECEF Z = 4322109.2 M                                                                             ECEF Z = 4321318.4 M                                         GEOID HT = -28.24 M                                                                              GEOID HT = -28.24 M                                          WGS ALT = 40.35 M WGS ALT = 37.51 M                                            ______________________________________                                    

NORTH AMERICAN DATUM OF 1983

NAD 83 is a reference datum for the earth replacing the North American Datum of 1927 (NAD 27). It was developed over many years through international efforts of many people. It was the largest single project ever undertaken by the National Geodetic Survey (NGS), spanning 12 years.

The task involved 1,785,772 survey observations at 266,436 sites in North and Central America, Greenland and the Caribbean Islands. The observations were made with all types of survey and measurement equipment from satellites to tape measures. The ultimate task was to develop and earth model which satisfied a set of 1,785,722 simultaneous equations. The task was performed using a least squares approach and Helmet blocking. The purpose was to update NAD 27, calculate geoid heights at 193,241 control points and the deflections of vertical at the control points.

The NAD 83 reference uses the Geodetic Reference System of 1980 (GRS 80) ellipsoid based on the Naval Surface Warfare Center 9Z-2 (NSWC 9Z-2) doppler measurements. The ellipsoid is positioned to be geocentric and have cartesian coordinate orientation consistent with the definition of Bureau International de l'Heure (BIH) Terrestrial System of 1984.

NAD 83 data sheets contain information to update North American 1927 references. The data sheets contain new information which is relevant for precise surveys and users of GPS equipment. These include: precise latitude and longitude [DDD MM SS.sssss], latitude--longitude shift in seconds of degree from NAD 27 to NAD 83, elevation above the geoid with standard error, geoid height and standard error, state plane and Universal Transverse Mercator (UTM) coordinates.

These fundamental corrections and ellipsoid constants are the basic parameters used in many coordinate conversions and navigational programs and form the basis of modern survey measurements.

GRS 80 used by NAD 83 has the following fundamental parameters:

    ______________________________________                                         NAD 83 PARAMETERS                                                              PARAMETER         VALUE        UNITS                                           ______________________________________                                         Semimajor axis*   6378137      M                                               Angular velocity* 7292115 × 10.sup.-11                                                                  RAD/SEC                                         Gravitational constant*                                                                          3986005 × 10.sup.8                                                                    M.sup.3 /SEC.sup.2                              Dynamic form factor unnormalized                                                                 108263 × 10.sup.-8                                     Semiminor axis*   6356752.314  M                                               Eccentricity squared                                                                             0.00669438002290                                             Flattening        0.00335281068118                                             Polar Radius of Curvature*                                                                       6399593.625  M                                               ______________________________________                                          (*Denotes values which are identical to WGS 84, underline denotes              differences between NAD 83 and WGS 84)                                   

WORLD GEODETIC SURVEY OF 1984

WGS 84 was developed by the U.S. Department of Defense. The reference system started with the same initial BIH conventions as NAD 83 but, over the development, some parameters changed slightly. The geocentric ECEF system is based on a cartesian coordinate system with its origin at the center of mass of the earth. The system defines the X and Y axis to be in the plane of the equator with the X axis anchored 0.554 arc seconds east of 0 longitude meridian and the Y axis rotated 90 degrees east of the X axis. The Z axis extends through the axis of rotation of the earth. The WGS 84 reference uses the GRS 80 ellipsoid as does NAD 83. WGS 84 includes slight changes to GRS 80 parameters which are identified below:

    ______________________________________                                         WGS 84 PARAMETERS                                                              PARAMETER        VALUE         UNITS                                           ______________________________________                                         Semimajor axis*  6378137       M                                               Angular velocity*                                                                               7292115 × 10.sup.-11                                                                   RAD/SEC                                         Gravitational constant*                                                                         3986005 × 10.sup.8                                                                     M.sup.3 /SEC.sup.2                              Dynamic form factor normalized                                                                  -484.16685 × 10.sup.-6                                  Semiminor axis*  6356752.314   M                                               Eccentricity squared                                                                            0.00669437999013                                              Flattening       0.00335281066474                                              Polar Radius of Curvature*                                                                      6399593.625   M                                               ______________________________________                                          (*Denotes values which are identical to NAD 83, underline indicates where      differences occur between NAD 83 and WGS 84)                             

COMPARISON OF NAD 83 AND WGS 84

The North American Datum of 1983 (NAD 83) and World Geodetic Survey of 1984 (WGS 84) attempt to describe the surface of the earth from two different perspectives. NAD 83 describes the surface of North America using the Geodetic Reference System of 1980 (GRS 80) ellipsoid and over 1.7 million actual measurements. A least squares Helmert blocking analysis was performed by National Geodetic Survey (NGS) on these measurements to determine the best fit solution to the actual measurements. NAD 83 uses monumented reference points across the country to precisely reference various coordinate systems such as the State Plane Coordinate Systems. WGS 84 incorporates positional references using GPS and local references. Position determination by GPS incorporates precise Keplerian orbital mechanics and radio positioning technology. Clearly, the two systems are describing the same thing, but the methods of determining a position are different.

Both NAD 83 and WGS 84 are based on BIH conventions. Though both are based on the GRS 80 ellipsoid, small changes have occurred between the two systems during their development. The basic difference in the dynamic form factor was attributed to GRS 80 using the unnormalized form while WGS 84 used a normalized form and rounded to eight significant figures. Since other parameters derived from the dynamic form factor differences usually appear after the eighth decimal place, most experts feel that the computational differences are of no significance.

Computations to determine the latitude and longitude from ECEF X,Y,Z coordinates highlight the small difference in the two reference systems. It has been shown that the maximum error between the two reference systems occurs at a latitude of 45 degrees. (Refer to North American Datum of 1983, Charles R. Schwartz) No error occurs between the two systems in the determination of longitude. The maximum error amounts to 0.000003 seconds of arc which amounts to a latitude shift of 0.0001 meters. For all practical purposes, the computational differences between the two systems are negligible. This is an important point for, if the two earth models differed in basic latitude and longitude computations, serious charting and navigational problems would occur and GPS navigation based on NAD 83 referenced maps would be seriously limited.

Both WGS 84 and NAD 83 have many common points used as local reference points. The differences between the two systems may reach several meters in rare locations, but on the average the systems should be identical. Generally, measurement errors and equipment inaccuracies introduce more error than the differences in the two systems.

For airport mapping and GPS navigation we can assume that errors due to the differences between the NAD 83 and WGS 84 ellipsoid models are negligible. This implies that either system can be used in calculating navigational entities and performing precise mapping with GPS navigation. The monumented New Hampshire points established on NAD 83 near the airport are well within the measurement accuracy of the GPS survey and navigation equipment. The documented offsets between NAD 83 and WGS 84 for New Hampshire are 0.0 meters in the Y direction and -0.5 meters in the X direction.

PHOTOGRAMMETRY

Photogrammetry techniques incorporating ground reference point(s) are recommended for creating electronic ALP's. Various techniques may be employed to generate digital ALP's including aerial photogrammetry and ground based moving platforms with integrated video cameras and sensors. The collected image data may be post processed to produce a highly accurate 2 or 3-digital map of the surrounding area.

A digital map of Manchester (NH) Airport was created to support early test activities. The digital map was based on aerial photogrammetry and GPS ground control using postprocessing software. A Wild Heerbrugg aerial camera equipped with forward motion compensation was used to capture the photogrammetry. The 3-D digitalization was performed using a Zeiss stereoscopic digitizing table. During the digitalization process, numerous object oriented map layers were constructed to segregate various types of map information. The resulting 3-D digital map had a relative horizontal accuracy of better than 1.0 meter and a relative vertical accuracy of better than 0.1 meter across the airport.

3-D GRAPHICS FORMATS

Many digital map formats are in widespread use today. Translators are available to convert from one computer format to another. Maps may be in either raster format (such as those generated by image scanning) or vector format (those developed on CAD and digitizing equipment). The vector format provides a much more robust environment for developers of ATC and map display systems. Vector based drawings are represented by individual vectors which can be controlled and modified individually or collectively. This enables the developer to manage these entities at a high level rather than at the individual pixel level. The vectors may represent specific geographical features (entities) in the map which may be assigned to a particular map layer in a particular user defined color.

Since the map and ATC situation display are in a vector format, a convenient method of graphically identifying and manipulating information is available. The selection of a graphical symbol on the screen through the use of a pointing device can be used to access an entity-related database or initiate an entity-based processing function. With raster-based images, there is no simple way to segregate the various pieces of map or graphic information for high level management.

Raster formats represent a series of individual pixels, each pixel controlled as a function of a series of control bits. Typically a series of three (3) words are used to describe the Red, Green and Blue (RGB) intensity of each pixel. Each pixel of information represents the smallest piece of the image and has no information about the larger graphical entity that it is part of. From a management perspective, this introduces additional complications for even the simplest graphical manipulation tasks such as suppressing the display of a series of raster based topographical contour lines in the airport map.

A high level management capability of required for ALP graphic entity control. The current raster-based maps do not provide this functionality, hence additional processing is required each time the map is displayed or modified. For raster-based maps to provide this capability, the pixel elements must be functionally organized in some manner to support the higher level management functions described in this application. For this reason, raster scan map formats are not recommended for ALPs at this time.

Vector formats may be in ASCII or binary and may be constructed using different rules for their generation. The example below uses the AutoCADTM DXF standard drawing format. (AutoCAD is a registered of AUTODESK, Inc.) AutoCADTM is one of the most popular Computer Aided Design (CAD) software packages in the world today and is typical of vector ALP formats. The DXF map format may be easily converted to almost any CAD drawing format.

    ______________________________________                                         AUTOCADTM DXF ALP FORMAT                                                       NEW HAMPSHIRE STATE PLANE                                                                             ECEF X, Y, Z                                            FEET                   METERS                                                  ______________________________________                                         3DFACE                 3DFACE                                                  8                      8                                                       BUILDING               BUILDING                                                10                     10                                                      1046289.75             1489279.59                                              20                     20                                                      154935.219             -4434265.78                                             30                     30                                                      256.499                4321428.53                                              11                     11                                                      1046289.75             1489277.26                                              21                     21                                                      154935.219             -4434258.83                                             31                     31                                                      223.7                  4321421.72                                              12                     12                                                      1046245.375            1489258.04                                              22                     22                                                      155032.25              -4434243.98                                             32                     32                                                      223.7                  4321443.43                                              13                     13                                                      1046245.375            1489260.37                                              23                     23                                                      155032.25              -4434250.92                                             33                     33                                                      256.499                4321450.24                                              0                      0                                                       ______________________________________                                    

The two formats shown above represent the vertical side of a building which is, by AutoCADTM convention, a 3-D face. Since the two coordinate systems are different, one must appropriately set the respective viewpoint for each display. This is accomplished in the initial ALP DXF configuration declarations. In a similar fashion, the drawing could be converted to other coordinate systems such as Universal Transverse Mercator (UTM) using a DXF coordinate conversion utility program such as TRALAINE™ (available from Mentor Software, Thornton, Colo.

The above example represents just one of the thousands of entities making up an ALP. Many commercial graphical libraries and commercial CAD software products are available today for the construction and use of ALPs and other 3-D graphic entities.

The use of modern digital Computer Aided Design (CAD) techniques is required for the development of electronic map databases. The use of GPS-based, ground referenced photogrammetry with post processing 2 or 3-D digitalization provides a cost effective, highly accurate and automated method of constructing the 2 or 3-D ALP.

An industry or international standard format for the construction and interchange of digital graphical information should be used. Numerous standards are established with readily available software translators for conversions between the various formats. Map file formats may be binary or ASCII characters.

3-D OBJECT ORIENTED MAP LAYERS

When stored in a digital format, the ALP should be arranged in object oriented map layers. Proper layering of information provides the capability to present only the information that is needed for a particular purpose. For example, navigational maps should not necessarily include all the digital layers of the ALP. A simplified version of the map showing only runways, taxiways, navigational references (landmarks) and gate areas should be used. The use of specific layers of interest provides the following advantages:

minimizes possible confusion in presenting too much information to the pilot or controller

decreases reaction time of controller and pilot by only presenting what is needed

reduces computer memory requirements

minimizes computer processing requirements

provides faster display updates (fewer pixels to redraw)

3-D DIGITAL MAP COORDINATE SYSTEMS

In order to integrate GPS navigational data with 2 or 3-D maps, the potential map formats must be evaluated for compatibility and ease of use with the navigational output and coordinate reference system. The table below lists twelve of the most likely combinations.

    ______________________________________                                         COMBINATIONS OF MAPS, NAVIGATIONAL PARAMETERS                                  AND MATHEMATICAL COORDINATE REFERENCES                                                      MATHEMATICAL                                                      DIGITAL      NAVIGATIONAL  COORDINATE                                          # MAP FORMAT I/O FORMAT    REFERENCE                                           ______________________________________                                         1. LAT, LON, MSL                                                                            LAT, LON, MSL LAT, LON, MSL                                       2.* LAT, LON, MSL                                                                           LAT, LON, MSL ECEF                                                3. LAT, LON, MSL                                                                            STATE PLANE/UTM                                                                              ECEF                                                4. LAT, LON, MSL                                                                            ECEF          ECEF                                                5. STATE PLANE/UTM                                                                          STATE PLANE/UTM                                                                              STATE PLANE/UTM                                     6. STATE PLANE/UTM                                                                          LAT, LON, MSL LAT, LON, MSL                                       7.* STATE PLANE/                                                                            LAT, LON, MSL ECEF                                                UTM                                                                            8. STATE PLANE/UTM                                                                          ECEF          ECEF                                                9. ECEF      ECEF          ECEF                                                10.*ECEF     LAT, LON, MSL ECEF                                                11. ECEF     LAT, LON, MSL LAT, LON, MSL                                       12. ECEF     STATE PLANE/UTM                                                                              STATE PLANE/UTM                                     ______________________________________                                          (UTM = Universal Transverse Mercator)                                    

Other permutations are possible for the different combinations of coordinate systems, map references and navigational output formats. Other combinations can be "made to work", but based on arithmetic precision, map availability and software complexity, the combinations identified with an asterisk satisfy the evaluation criteria most effectively.

The table below presents a compliance matrix, where each of the twelve combinations are evaluated against a set of criteria. The criteria used are described in greater detail following the table.

    ______________________________________                                         COMPLIANCY MATRIX                                                              MAPPING        *                     *           *                                                          FORMAT:                                                                        1-                                                                             2-                                                                             3-                                                                             4-                                                                             5-                                                                             6-                                                                             7-                                                                             8-                                                                             9- 10- 11- 12                                     ______________________________________                                                                      EXISTING Y Y Y Y Y Y Y Y N N N N                                               MAP DATA                                                                       RECOGNIZ- Y Y Y Y Y Y Y Y N N N N                                              ABLE MAP                                                                       CONV. SW Y Y Y Y Y Y Y Y Y Y Y Y                                               EXISTS                                                                         EASY 3D-2D Y Y Y Y Y Y Y Y N N N N                                             CONV                                                                           MULTI-USE Y Y Y Y Y Y Y Y N N N N                                              FORMAT                                                                         WORLD Y Y Y Y N N N N Y Y Y Y                                                  WIDE                                                                           SYSTEM                                                                         LINEAR N N N N Y Y Y Y Y Y Y Y                                                 SYSTEM                                                                         GPS Y Y Y Y N N N N Y Y Y Y                                                    COMPATIBLE                                                                     SEAMLESS N N N N N N N N Y Y Y Y                                               SYSTEM                                            ______________________________________                                                                      NAV INPUT-                                                                     OUTPUT:                                                                        1-                                                                             2-                                                                             3-                                                                             4-                                                                             5-                                                                             6-                                                                             7-                                                                             8-                                                                             9- 10- 11- 12                                     ______________________________________                                                                      RECOGNIZ- Y Y N N N Y Y N N Y Y N                                              ABLE                                                                           ACCEPTED Y Y N N N Y Y N N Y Y N                                               STANDARD                                                                       WORLD Y Y N Y N Y Y Y Y Y Y N                                                  WIDE USE                                                                       GPS Y Y N Y N Y Y Y Y Y Y N                                                    COMPATIBLE                                                                     CHARTS Y Y N N Y Y Y N N Y Y Y                                                 AVAILABLE                                         ______________________________________                                                                      COORD                                                                          REFERENCE:                                                                     1-                                                                             2-                                                                             3-                                                                             4-                                                                             5-                                                                             6-                                                                             7-                                                                             8-                                                                             9- 10- 11- 12                                     ______________________________________                                                                      RECOGNIZ- Y N N N Y Y N N N N Y Y                                              ABLE REF.                                                                      WORLD Y Y Y Y N Y Y Y Y Y Y N                                                  WIDE USE                                                                       SIMPLE NAV. N Y Y Y Y N Y Y Y Y N Y                                            MATH.                                                                          NAD83 & Y Y Y Y Y Y Y Y Y Y Y Y                                                WGS84 REF                                                                      SINGLE 3D N Y Y Y N N Y Y Y Y N N                                              ORIGIN                                                                         LINEAR N Y Y Y Y N Y Y Y Y N Y                                                 SYSTEM                                                                         UNITS OF N Y Y Y Y N Y Y Y Y N Y                                               DISTANCE                                          ______________________________________                                                                      TOTAL  *     *   *                                                             YES COUNT:                                                                     1-                                                                             2-                                                                             3-                                                                             4-                                                                             5-                                                                             6-                                                                             7-                                                                             8-                                                                             9- 10 11 12                                       ______________________________________                                                                       15 18 13 15 12 14 17 14 13 16 13 11              ______________________________________                                          *Suggested combinations                                                  

    MAPPING:    CRITERIA DEFINITIONS                                               ______________________________________                                         COMPATIBILITY                                                                              Existing digital map data is available                             WITH EXISTING                                                                              for the airport and surrounding area.                              MAP DATA                                                                       RECOGNIZABLE                                                                               A map which is instantly recognizable,                             MAP         one which resembles the surface on which                                       we live. The map should not need to be                                         differentially corrected from the reference geoid.                 CONVERSION SW                                                                              Commercially available software exists                             EXISTS      to convert from one 3-D map reference                                          system to the other                                                EASY 3D - 2D                                                                               Digital map presentations can be easily                            CONVERSION  converted from 3-D to 2-D by setting the                                       altitude to zero without any additional                                        mathematical conversions in the raw map                                        data or in the 3-D graphical interface.                            MULTI-USE   The map data is in a standard format                               FORMAT      which can satisfy multi-use needs such                                         as Master Plans, construction needs,                                           ATC and general navigation.                                        WORLD WIDE  References in the map are with respect                             SYSTEM      to world wide datums and accepted world                                        wide mapping units.                                                LINEAR SYSTEM                                                                              The axes and units of the map are                                              linear and represent distance.                                     GPS COMPATIBLE                                                                             Mapping units and presentations are                                            directly compatible with existing                                              GPS receiver output formats and                                                calculation references.                                            SEAMLESS SYSTEM                                                                            Maps do not have mathematical/physical                                         discontinuity, the map format must be                                          seamless on a world wide basis. For                                            example UTM maps do not cover polar                                            regions and map edges do not match on 6                                        degree boundaries when placed together.                            NAVIGATIONAL                                                                   OUTPUT:                                                                        RECOGNIZABLE                                                                               The final navigational output should be                                        instantly recognizable; i.e. if LAT,                                           LON, MSL output is used, one can                                               instantly visualize a location on the                                          earth, while if ECEF outputs are given                                         it is difficult to visually picture a point in space.              ACCEPTED    Navigational format is an                                          STANDARD    accepted standard; i.e. LAT, LON, MSL                              WORLD WIDE USE                                                                             The navigational format is usable                                              over the entire world.                                             GPS COMPATIBLE                                                                             Navigational format is compatible with                                         existing GPS receiver outputs.                                     CHARTS      Paper and digital charts are available.                            AVAILABLE                                                                      COORDINATE                                                                     REFERENCE:                                                                     WORLD WIDE USE                                                                             The coordinate reference system is                                             recognized throughout the world.                                   SIMPLE      The coordinate system lends itself to                              NAVIGATION  simple linear navigational mathematics.                            MATHEMATICS                                                                    NAD83 AND WGS84                                                                            The reference system is compatible with                            REF.        North American Datum of 1983 and                                               World Geodetic Survey of 1984.                                     SINGLE ORIGIN                                                                              The system has one and only one origin.                            LINEAR SYSTEM                                                                              The system is a linear coordinate                                              system.                                                            UNITS OF    The coordinate system is based on units                            DISTANCE    of distance rather than angle.                                     ______________________________________                                    

To illustrate differences between GPS trajectories displayed in maps using different coordinate systems, the following plot examples are provided. FIG. 12 shows a plan view of latitude versus longitude. FIG. 14 shows the same trajectory in ECEF X and Y coordinates. FIG. 13 depicts the MSL Altitude versus Time while FIG. 15 shows the ECEF X values versus Time. Note the distortion between the latitude, longitude, MSL altitude and the ECEF X,Y, and Z coordinates. (The small rectangles on each plot represent waypoints along the trajectory path.)

Plotting points in the map database requires that the navigational computations provide output which is compatible with the map database coordinates. Combination #7 in the previous Table includes a map database which is in a State Plane Coordinates System and a navigational output in latitude, longitude and MSL. Additional conversions are required to convert the navigational data to state plane coordinates prior to plotting the points in the map database. A more convenient map, navigational and coordinate reference frame is required.

ALP SUMMARY AND RECOMMENDATIONS

Future airport maps or modifications to existing maps should make every attempt to utilize recent technological advances in their construction. The following items are guidelines for future map development:

Precise, 3-D airport maps (ALPs) should be created and maintained for all major and reliever airports.

ALPs should be constructed to satisfy multiple user requirements.

Electronic graphical design tools should be used in ALP construction. Computer Aided Design tools should be used wherever possible.

Standard graphical formats (either ASCII character or industry standard binary file formats) should be used.

The concept of electronic layers should be used to identify and isolate entities in the map database.

Airport Reference Points (ARPs) should be located at precisely monumented positions around the airport. ARPs should be referenced to the coordinate systems of interest (such as LAT,LON,MSL, ECEF X,Y,Z and the SPCS).

At least three (3) ARPs, located within the airport confines in areas which are not likely to be disturbed, are recommended. Where possible, these points should be placed in the far corners of the airport to form a triangle. These points should be surveyed with GPS based survey equipment and monumented physically on the ground and within the digital map database.

ARPs should be recomputed as necessary to assure accuracy of the navigation and ATC functions. Re-monumentation may be required as a part of airport construction and expansion. Natural phenomena such as plate tectonics, may force re-monumentation of the airport. When ARP positions change more than 0.5 meters horizontally and 0.1 meters vertically, re-monumentation is recommended.

Areas used by aircraft such as runways, taxiways, gate areas and ramps should be surveyed to a horizontal accuracy of 0.5 meters horizontally and elevation to 0.1 meters.

The use of photogrammetry is suggested as an efficient means of creating a digital database of an existing airport.

Earth reference systems used for the various map projections should be the NAD 83 or WGS 84. Older, previously accepted datums which do not correlate with GPS navigation or surveys should be avoided.

ALPs should be compatible with cockpit instrumentation and ATC databases.

GPS calibration areas should be located at all gates or areas where aircraft remain stationary. These areas should be identified in the airport digital map. The purpose of the calibration area is to allow the pilot to check the accuracy of the on board GPS equipment.

Cost effective and highly accurate mapping technology is available to allow for the generation of multi-use maps which should be compatible with a host of platforms and potential uses. The exploitation of these common use maps will enhance master planning, aviation and Air Traffic Control (ATC) capabilities. Maps developed to national standards will provide a cost effective navigational and ATC data base.

SUMMARY, RAMIFICATION AND SCOPE

The presented invention provides a valuable enhancement to the current airport environment. This enhancement will result in safer air travel and more efficient operation of our currently capacity limited airports. Human blunders in the cockpit and in the control tower have cost hundred of lives in the past. Seamless airport operations will result in lower air traffic controller and pilot workloads through the use of automation processing. The advanced guidance and lighting system described herein provides a framework for seamless airport operations. The described system provides a processing environment which satisfies many of the International Civil Aviation Organization's requirements for Guidance, Surveillance, Control and Routing. The integrated lighting control capability with a visual depiction of active lights on the situation display allows the controller to ascertain the operational status of airport lights. The lighting system is based on GNSS compatible surveillance information combined with digital software databases. The system operates without the need for costly maintenance prone physically mounted sensors on the airport surface. The system is also adaptable from a software perspective to accommodate changes in the airport layout, hence requires no construction normally associated with airport surface sensors.

Advanced situational awareness displays showing travel paths, and clearance compatible mirrored navigation automation processing will reduce the likelihood of human blunders in the control tower and in the cockpit resulting in a safer airport environment. The elimination of out dated single function navigation and surveillance systems will result in significant cost savings for the airport authority and the FAA. The cost effective nature of this GNSS based airport control and management system will allow deployment at smaller airports resulting in safer operations and better on time performance throughout the whole aviation system.

It is obvious that minor changes may be made in the form and construction of the invention without departing from the material spirit thereof. It is not, however, desired to confine the invention to the exact form herein shown and described, but is desired to include all such as properly come within the scope claimed. 

We claim:
 1. A GNSS compatible airport lighting guidance and safety system based upon the movements of at least one vehicle of a plurality of vehicles, said plurality of vehicles, including aircraft and surface vehicular equipment operating at an airport, the airport lighting guidance and safety system comprising:a. a computer system with a lighting control interface and lighting control processor used in the control of airfield lighting; b. means of establishing a coordinate reference being Cartesian, 3 dimensional and GNSS compatible; c. means for establishing a static zones database, said static zones database representing spatial characteristics of at least one of a plurality of lighting control static zones described using said coordinate reference; d. means for storing said static zones database in said computer system; e. means to ascertain the position in said coordinate reference of at least one vehicle and storing said position in said computer system; f. means to perform zone incursion processing using said computer system; g. means to determine a zone incursion using said zone incursion processing based upon when said position enters a lighting control static zone of said static zones database and; h. means in said computer system to affect the state of said airfield lighting based upon said determined zone incursion, thereby providing airport lighting guidance.
 2. A GNSS compatible airport lighting guidance and safety system as recited in claim 1 further comprising:a. means to determine the exit of said position from an incurred lighting control static zone using said zone incursion processing, and b. means in said computer system to affect the state of said airfield lighting based upon said determined exit of said position from said incurred lighting control static zone.
 3. A GNSS compatible airport lighting guidance and safety system as recited in claim 1 further comprising:a. means for determining the cleared trajectory of at least one vehicle; b. means for determining which lighting control static zones contained in said static zones database intersect said cleared trajectory; c. means to determine a zone incursion result using said zone incursion processing based upon when said position incurs said lighting control static zone contained in said static zone database, and d. means in said computer system to mask said zone incursion result when said position is incurring a zone intersecting said cleared trajectory, thereby controlling the state of said airfield lights.
 4. A GNSS compatible airport lighting guidance and safety system as recited in claim 1 further comprising:a. means for determining the cleared trajectory of at least one vehicle; b. means for determining which lighting control static zones contained in said static zones database intersect said cleared trajectory; c. means to determine a zone incursion result using said zone incursion processing based upon when said position incurs said lighting control static zone contained in said static zone database, and d. means to determine when said zone incursion result is based upon said position of said vehicle incurring said lighting control static zone, without said vehicle having a cleared trajectory intersecting said lighting control static zone; and e. means in said computer system to activate said airfield lighting when said position is incurring said lighting control static zone without a cleared trajectory.
 5. A GNSS compatible method for airport lighting control and traffic guidance using a computer system with a lighting control interface for the automatic control of runway lighting comprised of takeoff and landing lights, based upon the movements of at least one vehicle of a plurality of vehicles, said plurality of vehicles including aircraft and surface vehicular equipment operating at an airport, said method comprising the steps of:a. adopting the Earth Centered Earth Fixed coordinate reference frame for processing by said computer system; b. selecting an airport, said selected airport referenced to said coordinate frame; c. establishing a static zones database, said static zones database representing spatial characteristics of at least one runway lighting control static zone described using said coordinate reference; d. ascertaining the position in said coordinate reference of said at least one vehicle and storing said position in said computer system; e. determining using zone incursion processing when said position incurs said runway lighting control static zone contained in said static zones database; f. determining if said at least one vehicle has been cleared to incur said runway lighting control static zone, and g. activating runway lighting indicating a runway incursion condition when said at least one vehicle has not been cleared to incur said runway lighting control static zone. 